CVE-2026-63812: f2fs: fix incorrect FI_NO_EXTENT handling in __destroy_extent_node()
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1f70ddb28a3c71df124da5fa4040c808116d6bb9, 20190e498057997532c7f186d081011f18e0a462, 58a5deb220bcac4c73bf58954c0845644c997487.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1f70ddb28a3c71df124da5fa4040c808116d6bb9, 20190e498057997532c7f186d081011f18e0a462, 58a5deb220bcac4c73bf58954c0845644c997487 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 19, 2026
- Updated
- Nov 10, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-665
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- b00e6950da9c0e4986f6e93c875d2b9184bdb220, 0559a0e962aacbb47519e26ee663be04b72dcb92, 7.1affected
- 42dd1c91f993431d0b399502479d00e6ad1bca71 and later · before 7e4d8f98be63f98856a5176b9188dada6e7ba9eeaffected · git
- ab1eaf9d5c99042f5b0243bf67a06283a4c0757f and later · before 58a5deb220bcac4c73bf58954c0845644c997487affected · git
- b0e4395870eb3441ddc959f6710b5f6ca61aff26 and later · before 20190e498057997532c7f186d081011f18e0a462affected · git
- ed78aeebef05212ef7dca93bd931e4eff67c113f and later · before edf12cbeeeabe799bd2ee21fdb5c336cce6fbad7affected · git
- ed78aeebef05212ef7dca93bd931e4eff67c113f and later · before 1f70ddb28a3c71df124da5fa4040c808116d6bb9affected · git
- 6.6.140 and later · before 6.6.144affected · semver
- 6.12.88 and later · before 6.12.95affected · semver
- 6.18.30 and later · before 6.18.38affected · semver
- 6.1.191 and later · before 6.2affected · semver
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.1.191 and later · before 6.2
- linux linux kernel6.6.140 and later · before 6.6.144
- linux linux kernel6.12.88 and later · before 6.12.95
- linux linux kernel6.18.30 and later · before 6.18.38
- linux linux kernel7.0.7 and later · before 7.1.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.95-1 | 6.12.95-1 |
| Debian:14 | linux | before 7.1.3-1 | 7.1.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-63809Jul 19, 2026 · bpf: use kvfree() for replaced sysctl write buffer31Monitor
- ← EarlierCVE-2026-63811Jul 19, 2026 · f2fs: read COW data with the original inode during atomic write22Monitor
- Later →CVE-2026-63813Jul 19, 2026 · Revert "f2fs: remove non-uptodate folio from the page cache in move_data_block"31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1f70ddb28a3c71df124da5fa4040c808116d6bb9 | Vendor (CNA) |
| Linux Linux | 20190e498057997532c7f186d081011f18e0a462 | Vendor (CNA) |
| Linux Linux | 58a5deb220bcac4c73bf58954c0845644c997487 | Vendor (CNA) |
| Linux Linux | 6.12.95 | Vendor (CNA) |
| Linux Linux | 6.18.38 | Vendor (CNA) |
| Linux Linux | 6.2 | Vendor (CNA) |
| Linux Linux | 6.6.144 | Vendor (CNA) |
| Linux Linux | 7.1 | Vendor (CNA) |
| Linux Linux | 7e4d8f98be63f98856a5176b9188dada6e7ba9ee | Vendor (CNA) |
| Linux Linux | edf12cbeeeabe799bd2ee21fdb5c336cce6fbad7 | Vendor (CNA) |
| debian:linux | 6.12.95-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-533980 days apartNFSD: Fix SECINFO_NO_NAME decode error cleanup39Monitor
- CVE-2026-643686 days apartmm/slab: do not limit zeroing to orig_size when only red zoning is enabled32Monitor
- CVE-2026-23253123 days apartmedia: dvb-core: fix wrong reinitialization of ringbuffer on reopen31Monitor
- CVE-2025-71128186 days aparterspan: Initialize options_len before referencing options.22Monitor
- CVE-2025-21906474 days apartwifi: iwlwifi: mvm: clean up ROC on failure22Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0576 · Jul 20, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-665 · Improper InitializationCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.