CVE-2026-63812
CVE.org · Published
- Record status
- Published
- Identifier year (not publication year)
- 2026
- Source publication
- Source updated
- Imported by cveboard
- Source snapshot
- cve_2026-10-24_midnight_baseline ·
CNA source text (English)
f2fs: fix incorrect FI_NO_EXTENT handling in __destroy_extent_node()
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.
Scoped product and version facts
Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.
Exploitation unknown; this catalogue does not assess exploitation.
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
unaffected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 42dd1c91f993431d0b399502479d00e6ad1bca71 | affected | git | 7e4d8f98be63f98856a5176b9188dada6e7ba9ee | Unavailable | None listed |
| ab1eaf9d5c99042f5b0243bf67a06283a4c0757f | affected | git | 58a5deb220bcac4c73bf58954c0845644c997487 | Unavailable | None listed |
| b0e4395870eb3441ddc959f6710b5f6ca61aff26 | affected | git | 20190e498057997532c7f186d081011f18e0a462 | Unavailable | None listed |
| ed78aeebef05212ef7dca93bd931e4eff67c113f | affected | git | edf12cbeeeabe799bd2ee21fdb5c336cce6fbad7 | Unavailable | None listed |
| ed78aeebef05212ef7dca93bd931e4eff67c113f | affected | git | 1f70ddb28a3c71df124da5fa4040c808116d6bb9 | Unavailable | None listed |
| 0559a0e962aacbb47519e26ee663be04b72dcb92 | affected | git | Unavailable | Unavailable | None listed |
| 6.6.140 | affected | semver | 6.6.144 | Unavailable | None listed |
| 6.12.88 | affected | semver | 6.12.95 | Unavailable | None listed |
| 6.18.30 | affected | semver | 6.18.38 | Unavailable | None listed |
| 7.0.7 | affected | semver | 7.1 | Unavailable | None listed |
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
affected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 7.1 | affected | Unavailable | Unavailable | Unavailable | None listed |
| 0 | unaffected | semver | 7.1 | Unavailable | None listed |
| 6.6.144 | unaffected | semver | Unavailable | 6.6.* | None listed |
| 6.12.95 | unaffected | semver | Unavailable | 6.12.* | None listed |
| 6.18.38 | unaffected | semver | Unavailable | 6.18.* | None listed |
| 7.1.3 | unaffected | semver | Unavailable | 7.1.* | None listed |
| 7.2 | unaffected | original_commit_for_fix | Unavailable | * | None listed |