CVE-2026-31666btrfs: fix incorrect return value after changing leaf in lookup_extent_data_ref()
- 7.8HighCVSS base score
- 0.12%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: btrfs: fix incorrect return value after changing leaf in lookup_extent_data_ref() After commit 1618aa3c2e01 ("btrfs: simplify return variables in lookup_extent_data_ref()"), the err and ret variables were merged into a single ret variable. However, when btrfs_next_leaf() returns 0 (success), ret is overwritten from -ENOENT to 0. If the first key in the next leaf does not match (different objectid or type), the function returns 0 instead of -ENOENT, making the caller believe the lookup succeeded when it did not. This can lead to operations on the wrong extent tree item, potentially causing extent tree corruption. Fix this by returning -ENOENT directly when the key does not match, instead of relying on the ret variable.
Timeline
ID reserved
By Linux
- 46 days later
· 46 days later
Published
- 6 months later
· 6 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 · Modified | 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.12% · top 98% of all CVEs (19 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 1618aa3c2e0163f5ac34d514ae89474521910536 – < 4125a194db4a6cf91f619f38788272651cb97dce
- affected 1618aa3c2e0163f5ac34d514ae89474521910536 – < 450e6a685d0cad95b15f8af152057bd0bf79f50b
- affected 1618aa3c2e0163f5ac34d514ae89474521910536 – < ab1e022379c3c811aa72da8eb0c7507859a1d0f5
- affected 1618aa3c2e0163f5ac34d514ae89474521910536 – < 316fb1b3169efb081d2db910cbbfef445afa03b9
- affected 6.10
- unaffected < 6.10
- unaffected 6.12.82 – ≤ 6.12.*
- unaffected 6.18.23 – ≤ 6.18.*
- unaffected 6.19.13 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References4
- https://git.kernel.org/stable/c/4125a194db4a6cf91f619f38788272651cb97dce (opens in a new tab)
- https://git.kernel.org/stable/c/450e6a685d0cad95b15f8af152057bd0bf79f50b (opens in a new tab)
- https://git.kernel.org/stable/c/ab1e022379c3c811aa72da8eb0c7507859a1d0f5 (opens in a new tab)
- https://git.kernel.org/stable/c/316fb1b3169efb081d2db910cbbfef445afa03b9 (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-25559 (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-31666)Record last updated .