Bug 2347905 (CVE-2022-49318) - CVE-2022-49318 kernel: f2fs: remove WARN_ON in f2fs_is_valid_blkaddr
Summary: CVE-2022-49318 kernel: f2fs: remove WARN_ON in f2fs_is_valid_blkaddr
Keywords:
Status: NEW
Alias: CVE-2022-49318
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-02-26 03:10 UTC by OSIDB Bzimport
Modified: 2025-06-04 14:29 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

Description OSIDB Bzimport 2025-02-26 03:10:52 UTC 
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.
Comment 1 Avinash Hanwate 2025-02-26 14:05:16 UTC 
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025022637-CVE-2022-49318-732e@gregkh/T
Comment 3 Avinash Hanwate 2025-02-28 00:09:51 UTC 
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025022637-CVE-2022-49318-732e@gregkh/T
Note You need to log in before you can comment on or make changes to this bug.