Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-31666: btrfs: fix incorrect return value after changing leaf in lookup_extent_data_ref()

HighCVSS 7.8 · v3.1—No exploit Fix available

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 316fb1b3169efb081d2db910cbbfef445afa03b9, 4125a194db4a6cf91f619f38788272651cb97dce, 450e6a685d0cad95b15f8af152057bd0bf79f50b.

Low priority for now. Upgrade to Linux Linux 316fb1b3169efb081d2db910cbbfef445afa03b9, 4125a194db4a6cf91f619f38788272651cb97dce, 450e6a685d0cad95b15f8af152057bd0bf79f50b 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: 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.

Published
Apr 24, 2026
Updated
Nov 11, 2026
EPSS
0.1% · 1th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

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.

Follow CVE-2026-31666

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
linuxlinux 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

    • 6.10affected
    • 1618aa3c2e0163f5ac34d514ae89474521910536 and later · before 4125a194db4a6cf91f619f38788272651cb97dceaffected · git
    • 1618aa3c2e0163f5ac34d514ae89474521910536 and later · before 450e6a685d0cad95b15f8af152057bd0bf79f50baffected · git
    • 1618aa3c2e0163f5ac34d514ae89474521910536 and later · before ab1e022379c3c811aa72da8eb0c7507859a1d0f5affected · git
    • 1618aa3c2e0163f5ac34d514ae89474521910536 and later · before 316fb1b3169efb081d2db910cbbfef445afa03b9affected · git
    • before 6.10not affected · semver
    • 6.12.82 and later · up to and including 6.12.*not affected · semver
    • 6.18.23 and later · up to and including 6.18.*not affected · semver
    • 6.19.13 and later · up to and including 6.19.*not affected · semver
    • 7.0 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:13linuxbefore 6.12.85-16.12.85-1
Debian:14linuxbefore 6.19.13-16.19.13-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-31664Apr 24, 2026 · xfrm: clear trailing padding in build_polexpire()
    22Monitor
  • ← EarlierCVE-2026-31665Apr 24, 2026 · netfilter: nft_ct: fix use-after-free in timeout object destroy
    31Monitor
  • Later →CVE-2026-31667Apr 24, 2026 · Input: uinput - fix circular locking dependency with ff-core
    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 / packageFixed versionSource
Linux Linux316fb1b3169efb081d2db910cbbfef445afa03b9Vendor (CNA)
Linux Linux4125a194db4a6cf91f619f38788272651cb97dceVendor (CNA)
Linux Linux450e6a685d0cad95b15f8af152057bd0bf79f50bVendor (CNA)
Linux Linuxab1e022379c3c811aa72da8eb0c7507859a1d0f5Vendor (CNA)
debian:linux6.12.85-1 · Debian:13Package 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.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-39682231 days aparttls: fix handling of zero-length records on the rx_listKEV
    70This week
  • CVE-2026-316370 days apartrxrpc: reject undecryptable rxkad response tickets
    39Monitor
  • CVE-2026-4313312 days apartKVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation
    31Monitor
  • CVE-2026-6384186 days apartdrm/amdgpu/jpeg: set no_user_fence for JPEG v5.0.1 ring
    31Monitor
  • CVE-2026-6384386 days apartdrm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.5 ring
    31Monitor
  • CVE-2026-6384786 days apartdrm/amdgpu/jpeg: set no_user_fence for JPEG v2.5 ring
    31Monitor

Not on record for this CVE: EPSS history · 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

CVSS 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.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records