CVE-2022-49318
Low
No strong exploitation signal.
CVSS base
5.5
MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS — probability of exploitation (30 days)
0.3%
17.7th percentile
CISA KEV
Not listed
Weakness / dates
—
Published 2025-02-26 · modified 2026-08-15
CVSS breakdown
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
| Attack Vector | L | Local |
| Attack Complexity | L | Low |
| Privileges Required | L | Low |
| User Interaction | N | None |
| Scope | U | Unchanged |
| Confidentiality | N | None |
| Integrity | N | None |
| Availability | H | High |
Timeline
- 2025-02-26 — Published (NVD)
- 2026-08-15 — Last modified (NVD)
Description
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
References
- https://git.kernel.org/stable/c/0a7a1fc7e71eecf2e5053a6c312c9f0dcbb9b8fd
- https://git.kernel.org/stable/c/32bea51fe4c6e92c00403739f7547c89219bea88
- https://git.kernel.org/stable/c/8c62c5e26345c34d199b4b8c8e69255ba3d0e751
- https://git.kernel.org/stable/c/99c09b298e47ebbe345a6da9f268b32a6b0f4582
- https://git.kernel.org/stable/c/cd6374af36cc548464d8c47a93fdba7303bb82a4
- https://git.kernel.org/stable/c/dc2f78e2d4cc844a1458653d57ce1b54d4a29f21