f2fs: remove WARN_ON in f2fs_is_valid_blkaddr
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c9b60788fc760d136211853f10ce73dc152d1f4a · < dc2f78e2d4cc844a1458653d57ce1b54d4a29f21| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's f2fs block validation can trigger two WARNs, including when a block address is outside the expected range. The reported call trace reaches the issue while mounting an f2fs filesystem; the input does not establish attacker access or authentication requirements.
Engineers running the Linux kernel with f2fs support should check their installations; affected versions are not specified.