CVE-2026-99574: f2fs: bound the SIT/NAT bitmaps by the checkpoint pack

Published Nov 20, 2026

In the Linux kernel, the following vulnerability has been resolved:

f2fs: bound the SIT/NAT bitmaps by the checkpoint pack

sitverbitmapbytesize and natverbitmapbytesize are used as memcpy lengths into and out of sbi->ckpt, which is sized from cppayload alone, and nothing compares either length against that allocation.

sanitycheckckpt() has checked these two fields since c77ec61ca0a4, which added them after a crafted image overran buildsitinfo(). That check ties each length to a segment count; it never compares either against the allocation, which is the half this adds.

Mounting over-reads in buildsitinfo() and buildnodemanager(), and the first checkpoint writes the same lengths back through the same pointers, so the over-read's contents reach the on-disk checkpoint. An unmount is enough; the filesystem does not have to be used.

Bound both ends the way bitmapptr() lays them out. The three branches differ, so a single sum of the two lengths would still admit a small overflow when cppayload is non-zero.

Affected Software

3 affected componentsFixes available
linux/kernel>=3.8.0<6.12.118
6.12.118
linux/kernel>=6.13.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  4. Compensating control

    Validate sit_ver_bitmap_bytesize and nat_ver_bitmap_bytesize individually against the checkpoint-pack allocation sized from cp_payload before using them for bitmap copies.

Frequently Asked Questions

1

Who is exposed to this issue?

Systems that mount an attacker-crafted F2FS filesystem image are exposed. The issue occurs during mounting in F2FS checkpoint bitmap handling.

2

What does an attacker need to exploit it?

An attacker needs to provide a crafted F2FS image with checkpoint bitmap length fields that exceed the checkpoint-pack allocation. No filesystem activity is required after mounting; unmounting is sufficient for data read beyond the allocation to be written back to the on-disk checkpoint.

3

Are existing checkpoint sanity checks sufficient protection?

No. The existing checks validate the bitmap lengths against segment counts, but do not ensure that either length fits within the allocation derived from cp_payload.

4

What is the effect if a vulnerable filesystem is mounted?

F2FS can read beyond the checkpoint allocation in build_sit_info() and build_node_manager(). On the first checkpoint write, including during unmount, those same lengths can cause the over-read contents to be written into the filesystem checkpoint.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203