Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-80808: ext4: stop retrying saturated xattr cache entries

—No exploit Fix available

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.19% (FIRST EPSS).
  • Fixed version: Linux Linux 119a2f053242ed75bdd2ebc95baf3ae7db6ccacf, 4.20, 4902a5cba21aeaf91e6b29e20e0967a5f6abdcd9; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.

Low priority for now. Upgrade to Linux Linux 119a2f053242ed75bdd2ebc95baf3ae7db6ccacf, 4.20, 4902a5cba21aeaf91e6b29e20e0967a5f6abdcd9; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 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: ext4: stop retrying saturated xattr cache entries ext4_xattr_block_set() retries when a cache entry selected for reuse has a saturated reference count after taking the buffer lock. The retry returns to the mbcache lookup without making that entry ineligible, so it can select the same unusable entry indefinitely. A task spinning there can hold the parent directory's i_rwsem and leave concurrent rmdir callers blocked. Normally a reusable entry has a reference count below EXT4_XATTR_REFCOUNT_MAX because the count and MBE_REUSABLE_B are updated under the same buffer lock. A corrupted filesystem can violate that invariant. The syzbot reproducer reports allocator and xattr corruption before triggering this retry loop. Check the untrusted on-disk count before incrementing it, avoiding overflow, and clear MBE_REUSABLE_B when it is already saturated. The next lookup then skips the entry that was just proven unusable. This mirrors the normal transition at EXT4_XATTR_REFCOUNT_MAX; the release path marks the entry reusable again on the exact 1024-to-1023 transition. Using the same QEMU harness and guest parameters, current unpatched Linux hung in 6 of 8 420-second trials with the do_rmdir signature; representative NMI backtraces caught the owner spinning in ext4_xattr_block_set(). The patched kernel completed 28 of 28 trials without a hung-task report; the final twelve trials exercised the reviewed overflow-safe form of the change. syzbot's patch testing also completed without reproducing the hang.

Published
Sep 4, 2026
Updated
Nov 6, 2026
EPSS
0.1% · 9th 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.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

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

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.

—

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

    • 98953044b3cdb2cb7d82e7365b659e2ed4f4ca4d, af8ecc8d20e72130771cc076bce7fcf17ccda6c4, c6fac5cf5a5098732623bcd00a8a3eb9f5465144, 96fa141fa295ae9428da73c56c9852053b575c04, 6.0affected
    • 1a56cd972ce121b6cf2517a47a578782bbd2ec95 and later · before 119a2f053242ed75bdd2ebc95baf3ae7db6ccacfaffected · git
    • 1be97463696c7291a3e1547614e96432b0bd3add and later · before 61631352a5b405c89be579de00903b72e6888aa4affected · git
    • 65f8b80053a1b2fd602daa6814e62d6fa90e5e9b and later · before 8865cd664484517703df5c18a965dc3227572b87affected · git
    • 65f8b80053a1b2fd602daa6814e62d6fa90e5e9b and later · before a40c45268f4358207aa9c53764fed2e05f62986aaffected · git
    • 65f8b80053a1b2fd602daa6814e62d6fa90e5e9b and later · before 889ec86464d261f026f6c334040cfc6c58c99d58affected · git
    • 65f8b80053a1b2fd602daa6814e62d6fa90e5e9b and later · before 4902a5cba21aeaf91e6b29e20e0967a5f6abdcd9affected · git
    • 65f8b80053a1b2fd602daa6814e62d6fa90e5e9b and later · before 55ee6533c1db7f7656fa8dd19637f3f8b8c08dc5affected · git
    • 65f8b80053a1b2fd602daa6814e62d6fa90e5e9b and later · before dbd4aea175ad3c46436acb251e817b4374628072affected · git
    • 65f8b80053a1b2fd602daa6814e62d6fa90e5e9b and later · before 54b6bd40898de7906acb2bccc9a96d1b8e6b4323affected · git

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.187-16.1.187-1
Debian:12linux-6.12before 6.12.107-1~deb12u16.12.107-1~deb12u1
Debian:13linuxbefore 6.12.107-16.12.107-1
Debian:14linuxbefore 7.1.12-17.1.12-1

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-80806Sep 4, 2026 · ext4: don't enable DAX on new encrypted files
    0Monitor
  • ← EarlierCVE-2026-80807Sep 4, 2026 · nilfs2: reject invalid block index in GC ioctl
    0Monitor
  • Later →CVE-2026-80809Sep 4, 2026 · ocfs2: fix missing metadata reservation for large xattrs
    0Monitor

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 Linux119a2f053242ed75bdd2ebc95baf3ae7db6ccacfVendor (CNA)
Linux Linux4.20Vendor (CNA)
Linux Linux4902a5cba21aeaf91e6b29e20e0967a5f6abdcd9Vendor (CNA)
Linux Linux5.10.267Vendor (CNA)
Linux Linux5.15.218Vendor (CNA)
Linux Linux5.19Vendor (CNA)
Linux Linux5.20Vendor (CNA)
Linux Linux5.5Vendor (CNA)
Linux Linux54b6bd40898de7906acb2bccc9a96d1b8e6b4323Vendor (CNA)
Linux Linux55ee6533c1db7f7656fa8dd19637f3f8b8c08dc5Vendor (CNA)
Linux Linux61631352a5b405c89be579de00903b72e6888aa4Vendor (CNA)
Linux Linux8865cd664484517703df5c18a965dc3227572b87Vendor (CNA)
Linux Linux889ec86464d261f026f6c334040cfc6c58c99d58Vendor (CNA)
Linux Linuxa40c45268f4358207aa9c53764fed2e05f62986aVendor (CNA)
Linux Linuxdbd4aea175ad3c46436acb251e817b4374628072Vendor (CNA)
azl3 kernel 6.6.150.1-1 on Azure Linux 3.0—Microsoft (MSRC)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.06.6.157.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.107-1~deb12u1 · Debian:12Package 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).

Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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.

References

All records