Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-90259: btrfs: qgroup: fix a wrong length calculation in qgroup_free_reserved_data()

Noroxi assessment

Priority: Monitor (action score 0/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.20% (FIRST EPSS).
  • Fixed version: Linux Linux 036e6c216be66a085da3a0519f1be5f3230b6e26, 202ac9e469b78817512921c5db05cc2140e4ca43, 34adc843c28e5cd1f533a1d64f51b0f756fdf945.

Low priority for now. Upgrade to Linux Linux 036e6c216be66a085da3a0519f1be5f3230b6e26, 202ac9e469b78817512921c5db05cc2140e4ca43, 34adc843c28e5cd1f533a1d64f51b0f756fdf945 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: qgroup: fix a wrong length calculation in qgroup_free_reserved_data() In that function, we round down the start position and round up the ending position. But during the calculation of @len, we use "round_up(start + len, sectorsize)", which is the rounded up end position, not the rounded up length. Which results a much larger length, and later we are still using "start + len", which is completely incorrect. Fix it by declaring a local @aligned_start and @aligned_len and use them instead.

—No exploit Fix available
Published
Sep 17, 2026
Updated
Oct 30, 2026
EPSS
0.2% · 10th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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-90259

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

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack 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 (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

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

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.

—

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

    • 4.13affected
    • bc42bda22345efdb5d8b578d1b4df2c6eaa85c58 and later · before 036e6c216be66a085da3a0519f1be5f3230b6e26affected · git
    • bc42bda22345efdb5d8b578d1b4df2c6eaa85c58 and later · before 202ac9e469b78817512921c5db05cc2140e4ca43affected · git
    • bc42bda22345efdb5d8b578d1b4df2c6eaa85c58 and later · before 34adc843c28e5cd1f533a1d64f51b0f756fdf945affected · git
    • bc42bda22345efdb5d8b578d1b4df2c6eaa85c58 and later · before e6edde29990af8064b9d12217ec03db231ccd55daffected · git
    • bc42bda22345efdb5d8b578d1b4df2c6eaa85c58 and later · before c4c136555ff90f1e2921cc42da43daac0ef9985eaffected · git
    • bc42bda22345efdb5d8b578d1b4df2c6eaa85c58 and later · before 9102b179512e11644fb0489ae62010a09afa199caffected · git
    • before 4.13not affected · semver
    • 6.1.191 and later · up to and including 6.1.*not affected · semver
    • 6.6.160 and later · up to and including 6.6.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:14linuxbefore 7.2.6-17.2.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-90257Sep 17, 2026 · Bluetooth: virtio_bt: avoid OOB read of build info string
    0Monitor
  • ← EarlierCVE-2026-90258Sep 17, 2026 · pinctrl: airoha: add missed IRQ resource helpers
    0Monitor
  • Later →CVE-2026-90260Sep 17, 2026 · btrfs: zoned: don't clobber the extent buffer when zeroing it out
    28Monitor

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 Linux036e6c216be66a085da3a0519f1be5f3230b6e26Vendor (CNA)
Linux Linux202ac9e469b78817512921c5db05cc2140e4ca43Vendor (CNA)
Linux Linux34adc843c28e5cd1f533a1d64f51b0f756fdf945Vendor (CNA)
Linux Linux9102b179512e11644fb0489ae62010a09afa199cVendor (CNA)
Linux Linuxc4c136555ff90f1e2921cc42da43daac0ef9985eVendor (CNA)
Linux Linuxe6edde29990af8064b9d12217ec03db231ccd55dVendor (CNA)
debian:linux7.2.6-1 · Debian:14Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

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

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records