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.
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
CVE-2026-63812 is a data integrity vulnerability in the Linux kernel's F2FS (Flash-Friendly File System) that occurs when the __destroy_extent_node() function improperly handles extent tree flags. Specifically, when setting the FI_NO_EXTENT flag to prevent future extent tree modifications, the function fails to reset the cached largest extent length to zero and update the inode folio, leaving stale extent metadata in memory. This affects Linux systems using F2FS, particularly those running storage-intensive workloads or using flash-based storage devices. The vulnerability can trigger sanity check failures and filesystem errors, potentially leading to data corruption or denial of service when the stale cache causes inconsistencies between in-memory state and on-disk metadata.
While this CVE currently has no mapped MITRE ATT&CK techniques or CWE classification, practitioners using Casky's extended reasoning capabilities would detect exploitation patterns by analyzing kernel log anomalies, filesystem integrity check failures, and inode state inconsistencies. The vulnerability represents a Resource Hijacking and Data Destruction threat pattern—attackers could trigger repeated extent cache invalidations to exhaust filesystem resources or corrupt file metadata. Casky practitioners would identify the attack through monitoring for repeated "sanity_check_extent_cache" failures, unexpected FI_NO_EXTENT flag transitions, and folio update anomalies that deviate from normal F2FS operational patterns, enabling early detection of filesystem-level exploitation attempts.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-63812. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation