CVE-2022-49318
published 2025-02-26CVE-2022-49318: In the Linux kernel, the following vulnerability has been resolved: f2fs: remove WARN_ON in f2fs_is_valid_blkaddr Syzbot triggers two WARNs in…
PriorityP418medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.26%
17.2th percentile
In the Linux kernel, the following vulnerability has been resolved:
f2fs: remove WARN_ON in f2fs_is_valid_blkaddr
Syzbot triggers two WARNs in f2fs_is_valid_blkaddr and
__is_bitmap_valid. For example, in f2fs_is_valid_blkaddr,
if type is DATA_GENERIC_ENHANCE or DATA_GENERIC_ENHANCE_READ,
it invokes WARN_ON if blkaddr is not in the right range.
The call trace is as follows:
f2fs_get_node_info+0x45f/0x1070
read_node_page+0x577/0x1190
__get_node_page.part.0+0x9e/0x10e0
__get_node_page
f2fs_get_node_page+0x109/0x180
do_read_inode
f2fs_iget+0x2a5/0x58b0
f2fs_fill_super+0x3b39/0x7ca0
Fix these two WARNs by replacing WARN_ON with dump_stack.
Affected
17 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.18.5-1 (bookworm) | linux 5.18.5-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 < 0a7a1fc7e71eecf2e5053a6c312c9f0dcbb9b8fd | 0a7a1fc7e71eecf2e5053a6c312c9f0dcbb9b8fd |
| linux | linux | >= 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 < 32bea51fe4c6e92c00403739f7547c89219bea88 | 32bea51fe4c6e92c00403739f7547c89219bea88 |
| linux | linux | >= 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 < 99c09b298e47ebbe345a6da9f268b32a6b0f4582 | 99c09b298e47ebbe345a6da9f268b32a6b0f4582 |
| linux | linux | >= 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 < cd6374af36cc548464d8c47a93fdba7303bb82a4 | cd6374af36cc548464d8c47a93fdba7303bb82a4 |
| linux | linux | >= 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 < 8c62c5e26345c34d199b4b8c8e69255ba3d0e751 | 8c62c5e26345c34d199b4b8c8e69255ba3d0e751 |
| linux | linux | >= 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 < dc2f78e2d4cc844a1458653d57ce1b54d4a29f21 | dc2f78e2d4cc844a1458653d57ce1b54d4a29f21 |
| linux | linux_kernel | < 5.4.198 | 5.4.198 |
| linux | linux_kernel | >= 0 < 5.10.127-1 | 5.10.127-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 5.11 < 5.15.47 | 5.15.47 |
| linux | linux_kernel | >= 5.16 < 5.17.15 | 5.17.15 |
| linux | linux_kernel | >= 5.18 < 5.18.4 | 5.18.4 |
| linux | linux_kernel | >= 5.5 < 5.10.122 | 5.10.122 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: f2fs: remove WARN_ON in f2fs_is_valid_blkaddr
vendor_redhat·2025-02-26·CVSS 5.5
CVE-2022-49318 [MEDIUM] kernel: f2fs: remove WARN_ON in f2fs_is_valid_blkaddr
kernel: f2fs: remove WARN_ON in f2fs_is_valid_blkaddr
In the Linux kernel, the following vulnerability has been resolved:
f2fs: remove WARN_ON in f2fs_is_valid_blkaddr
Syzbot triggers two WARNs in f2fs_is_valid_blkaddr and
__is_bitmap_valid. For example, in f2fs_is_valid_blkaddr,
if type is DATA_GENERIC_ENHANCE or DATA_GENERIC_ENHANCE_READ,
it invokes WARN_ON if blkaddr is not in the right range.
The call trace is as follows:
f2fs_get_node_info+0x45f/0x1070
read_node_page+0x577/0x1190
__get_node_page.part.0+0x9e/0x10e0
__get_node_page
f2fs_get_node_page+0x109/0x180
do_read_inode
f2fs_iget+0x2a5/0x58b0
f2fs_fill_super+0x3b39/0x7ca0
Fix these two WARNs by replacing WARN_ON with dump_stack.
Package: kernel (Red Hat Enterprise Linux 10) - Not affected
Package: kernel (Red Hat Enterprise Lin
Debian
CVE-2022-49318: linux - In the Linux kernel, the following vulnerability has been resolved: f2fs: remov...
vendor_debian·2022·CVSS 5.5
CVE-2022-49318 [MEDIUM] CVE-2022-49318: linux - In the Linux kernel, the following vulnerability has been resolved: f2fs: remov...
In the Linux kernel, the following vulnerability has been resolved: f2fs: remove WARN_ON in f2fs_is_valid_blkaddr Syzbot triggers two WARNs in f2fs_is_valid_blkaddr and __is_bitmap_valid. For example, in f2fs_is_valid_blkaddr, if type is DATA_GENERIC_ENHANCE or DATA_GENERIC_ENHANCE_READ, it invokes WARN_ON if blkaddr is not in the right range. The call trace is as follows: f2fs_get_node_info+0x45f/0x1070 read_node_page+0x577/0x1190 __get_node_page.part.0+0x9e/0x10e0 __get_node_page f2fs_get_node_page+0x109/0x180 do_read_inode f2fs_iget+0x2a5/0x58b0 f2fs_fill_super+0x3b39/0x7ca0 Fix these two WARNs by replacing WARN_ON with dump_stack.
Scope: local
bookworm: resolved (fixed in 5.18.5-1)
bullseye: resolved (fixed in 5.10.127-1)
forky: resolved (fixed in 5.18.5-1)
sid: resolved (fixed in 5.18
GHSA
GHSA-qh32-f63v-gpm9: In the Linux kernel, the following vulnerability has been resolved:
f2fs: remove WARN_ON in f2fs_is_valid_blkaddr
Syzbot triggers two WARNs in f2fs_
ghsa_unreviewed·2025-04-14
CVE-2022-49318 [MEDIUM] GHSA-qh32-f63v-gpm9: In the Linux kernel, the following vulnerability has been resolved:
f2fs: remove WARN_ON in f2fs_is_valid_blkaddr
Syzbot triggers two WARNs in f2fs_
In the Linux kernel, the following vulnerability has been resolved:
f2fs: remove WARN_ON in f2fs_is_valid_blkaddr
Syzbot triggers two WARNs in f2fs_is_valid_blkaddr and
__is_bitmap_valid. For example, in f2fs_is_valid_blkaddr,
if type is DATA_GENERIC_ENHANCE or DATA_GENERIC_ENHANCE_READ,
it invokes WARN_ON if blkaddr is not in the right range.
The call trace is as follows:
f2fs_get_node_info+0x45f/0x1070
read_node_page+0x577/0x1190
__get_node_page.part.0+0x9e/0x10e0
__get_node_page
f2fs_get_node_page+0x109/0x180
do_read_inode
f2fs_iget+0x2a5/0x58b0
f2fs_fill_super+0x3b39/0x7ca0
Fix these two WARNs by replacing WARN_ON with dump_stack.
OSV
CVE-2022-49318: In the Linux kernel, the following vulnerability has been resolved: f2fs: remove WARN_ON in f2fs_is_valid_blkaddr Syzbot triggers two WARNs in f2fs_is
osv·2025-02-26·CVSS 5.5
CVE-2022-49318 [MEDIUM] CVE-2022-49318: In the Linux kernel, the following vulnerability has been resolved: f2fs: remove WARN_ON in f2fs_is_valid_blkaddr Syzbot triggers two WARNs in f2fs_is
In the Linux kernel, the following vulnerability has been resolved: f2fs: remove WARN_ON in f2fs_is_valid_blkaddr Syzbot triggers two WARNs in f2fs_is_valid_blkaddr and __is_bitmap_valid. For example, in f2fs_is_valid_blkaddr, if type is DATA_GENERIC_ENHANCE or DATA_GENERIC_ENHANCE_READ, it invokes WARN_ON if blkaddr is not in the right range. The call trace is as follows: f2fs_get_node_info+0x45f/0x1070 read_node_page+0x577/0x1190 __get_node_page.part.0+0x9e/0x10e0 __get_node_page f2fs_get_node_page+0x109/0x180 do_read_inode f2fs_iget+0x2a5/0x58b0 f2fs_fill_super+0x3b39/0x7ca0 Fix these two WARNs by replacing WARN_ON with dump_stack.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://git.kernel.org/stable/c/0a7a1fc7e71eecf2e5053a6c312c9f0dcbb9b8fdhttps://git.kernel.org/stable/c/32bea51fe4c6e92c00403739f7547c89219bea88https://git.kernel.org/stable/c/8c62c5e26345c34d199b4b8c8e69255ba3d0e751https://git.kernel.org/stable/c/99c09b298e47ebbe345a6da9f268b32a6b0f4582https://git.kernel.org/stable/c/cd6374af36cc548464d8c47a93fdba7303bb82a4https://git.kernel.org/stable/c/dc2f78e2d4cc844a1458653d57ce1b54d4a29f21
2025-02-26
Published