CVE-2026-63812f2fs: fix incorrect FI_NO_EXTENT handling in __destroy_extent_node()
- 7.8HighCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Analyzed | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 98% of all CVEs (19 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 42dd1c91f993431d0b399502479d00e6ad1bca71 – < 7e4d8f98be63f98856a5176b9188dada6e7ba9ee
- affected ab1eaf9d5c99042f5b0243bf67a06283a4c0757f – < 58a5deb220bcac4c73bf58954c0845644c997487
- affected b0e4395870eb3441ddc959f6710b5f6ca61aff26 – < 20190e498057997532c7f186d081011f18e0a462
- affected ed78aeebef05212ef7dca93bd931e4eff67c113f – < edf12cbeeeabe799bd2ee21fdb5c336cce6fbad7
- affected ed78aeebef05212ef7dca93bd931e4eff67c113f – < 1f70ddb28a3c71df124da5fa4040c808116d6bb9
- affected b00e6950da9c0e4986f6e93c875d2b9184bdb220
- affected 0559a0e962aacbb47519e26ee663be04b72dcb92
- affected 6.6.140 – < 6.6.144
- affected 6.12.88 – < 6.12.95
- affected 6.18.30 – < 6.18.38
- affected 6.1.191 – < 6.2
- affected 7.0.7 – < 7.1
- affected 7.1
- unaffected < 7.1
- unaffected 6.6.144 – ≤ 6.6.*
- unaffected 6.12.95 – ≤ 6.12.*
- unaffected 6.18.38 – ≤ 6.18.*
- unaffected 7.1.3 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References5
- https://git.kernel.org/stable/c/7e4d8f98be63f98856a5176b9188dada6e7ba9ee (opens in a new tab)
- https://git.kernel.org/stable/c/58a5deb220bcac4c73bf58954c0845644c997487 (opens in a new tab)
- https://git.kernel.org/stable/c/20190e498057997532c7f186d081011f18e0a462 (opens in a new tab)
- https://git.kernel.org/stable/c/edf12cbeeeabe799bd2ee21fdb5c336cce6fbad7 (opens in a new tab)
- https://git.kernel.org/stable/c/1f70ddb28a3c71df124da5fa4040c808116d6bb9 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-45478 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-63812)Record last updated .