CVE Catalog

CVE-2026-63812

HighCVSS 7.8
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.12%

2th percentile - higher than 2% of all known CVEs

Summary

In the Linux kernel's F2FS filesystem, a vulnerability was found in the __destroy_extent_node() function where setting the FI_NO_EXTENT flag does not reset the largest extent length to zero or update the inode folio, causing stale cached data and triggering a sanity check error.

Risk Assessment

The risk involves potential data integrity corruption in the F2FS filesystem, leading to read/write errors and requiring fsck to repair.

Recommendation

Immediately update the Linux kernel to a version containing the fix that removes the unnecessary et->node_cnt check and resets the largest extent length when setting the FI_NO_EXTENT flag.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix incorrect FI_NO_EXTENT handling in __destroy_extent_node() When __destroy_extent_node() sets the inode flag FI_NO_EXTENT, it does not reset the length of the largest extent to 0 and update the inode folio. Since modifications to the extent tree are disallowed afterward, the cached largest extent may become stale. This can trigger the following error in xfstests generic/388: F2FS-fs (dm-0): sanity_check_extent_cache: inode (ino=1761) extent info [220057, 57, 6] is incorrect, run fsck to fix In the f2fs_drop_inode path, __destroy_extent_node() does not need to guarantee that et->node_cnt is 0, because concurrency with writeback is expected in this path, and writeback may update the extent cache. This patch reverts commit ed78aeebef05 ("f2fs: fix node_cnt race between extent node destroy and writeback"), and remove the unnecessary zero check of et->node_cnt.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS