VulnWatch by ve1ve2
high 7.8 EPSS 0.20%

CVE-2026-99574: In the Linux kernel, the following vulnerability has been resolved: f2fs: bound the SIT/NAT bitmaps by the checkpoint pack sit_ver_bitmap_bytesize and nat_ver_…

Source:
NVD CVE API 2.0
Published:
Fetched:
Updated:
Affects:
linux

https://nvd.nist.gov/vuln/detail/CVE-2026-99574 ↗

In the Linux kernel, the following vulnerability has been resolved: f2fs: bound the SIT/NAT bitmaps by the checkpoint pack sit_ver_bitmap_bytesize and nat_ver_bitmap_bytesize are used as memcpy lengths into and out of sbi->ckpt, which is sized from cp_payload alone, and nothing compares either length against that allocation. sanity_check_ckpt() has checked these two fields since c77ec61ca0a4, which added them after a crafted image overran build_sit_info(). 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 build_sit_info() and build_node_manager(), 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 __bitmap_ptr() lays them out. The three branches differ, so a single sum of the two lengths would still admit a small overflow when cp_payload is non-zero. References: https://git.kernel.org/stable/c/080833a32fd5dc10b3acf2fa9af9b3213e6cb617 https://git.kernel.org/stable/c/7f88cd38394a16c326073c8813e7f1f1445bf3ba https://git.kernel.org/stable/c/9b08fc2d092171af388f83030d54488b87453155 https://git.kernel.org/stable/c/ddb9848fd6b2f4e9ed5ef78b20c9720c65a29df5

Linked vulnerabilities (1)

CVE-2026-99574 high 7.8 EPSS 0.20% (p10) NVDCVE.org
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

kernel: kernel: Information disclosure in f2fs via crafted checkpoint bitmaps

CWE: CWE-125Aliases: CVE-2026-99272, CVE-2026-99275, CVE-2026-99308, CVE-2026-99312, CVE-2026-99314, CVE-2026-99315, CVE-2026-99316, CVE-2026-99317, CVE-2026-99318, CVE-2026-99319, CVE-2026-99320, CVE-2026-99335, CVE-2026-99336, CVE-2026-99345, CVE-2026-99347, CVE-2026-99348, CVE-2026-99350, CVE-2026-99363, CVE-2026-99376, CVE-2026-99377, CVE-2026-99379, CVE-2026-99382, CVE-2026-99384, CVE-2026-99387, CVE-2026-99394, CVE-2026-99426, CVE-2026-99484, CVE-2026-99496, CVE-2026-99566, CVE-2026-99567, CVE-2026-99568, CVE-2026-99569, CVE-2026-99570, CVE-2026-99573, CVE-2026-99575, CVE-2026-99576, CVE-2026-99577, CVE-2026-99578, CVE-2026-99579, CVE-2026-99580, CVE-2026-99582, CVE-2026-99583, CVE-2026-99587, CVE-2026-99588, CVE-2026-99589, CVE-2026-99590, CVE-2026-99591, CVE-2026-99593, CVE-2026-99594NVD: Received

Also reported by (1)