Linux Kernel: security vulnerability (CVE-2026-80808)
Published Last modified Sources: Ubuntu, HKCERT, Debian LTS, SUSE, CVE.org, BSI, EUVD, Msrc Update Guide
What is affected, what to do
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.
Update Linux Kernel to version 5.10.267, Linux Kernel to version 5.15.218, Linux Kernel to version 4.20.
- Affected
- Linux Kernel
lt 5.10.163..5.10.267 - Linux Kernel
lt 5.15.61..5.15.218 - Linux Kernel
lt 4.19.270..4.20 - Linux Kernel
lt 5.4.229..5.5 - Linux Kernel
lt 5.18.18..5.19 - Linux Kernel
lt 5.19.2..5.20 - Linux Kernel
lt 6.0..6.1.185 - Linux Kernel
lt 6.2..6.6.154 - Linux Kernel
lt 6.7..6.12.106 - Linux Kernel
lt 6.13..6.18.47 - Linux Kernel
lt 6.19..7.1.11 - Linux Kernel
lt 7.2..7.2.1
- Linux Kernel
- Fixed in
- Linux Kernel
5.10.267 - Linux Kernel
5.15.218 - Linux Kernel
4.20 - Linux Kernel
5.5 - Linux Kernel
5.19 - Linux Kernel
5.20 - Linux Kernel
6.1.185 - Linux Kernel
6.6.154 - Linux Kernel
6.12.106 - Linux Kernel
6.18.47 - Linux Kernel
7.1.11 - Linux Kernel
7.2.1 - Linux Kernel
7.3
- Linux Kernel
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
4.1
XIEM Effective CVSS
Highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v3
4.1
CVSS v3
Severity Medium on the scale from 0 to 10.
Source: Ubuntu, HKCERT, Debian LTS, SUSE, CVE.org, BSI, EUVD, Msrc Update Guide
0.2 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 9.3
Show all metrics
- Severity
- Medium
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 45.26 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 4.1 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 4.1
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.2 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 9.3
- Low — this CVE sits in the lower 10% of all CVEs scored today.
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
- CISA assessment (SSVC)
- Exploitation: none known · not automatable · Technical impact: partial
- Source: CISA Vulnrichment, as of 6 November 2026
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
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.
Source: Ubuntu Security Notices, HKCERT (CC BY 3.0 HK) · HKCERT rating: medium, Debian LTS Advisories, suse_csaf, cvelistv5, BSI WID Portal, BSI CSAF, NVD (NIST), CVE.org (MITRE), ENISA EUVD, Microsoft Security Update Guide
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Linux | Linux |
|
|
| Red Hat | OpenShift |
|
|
Vendors and products
Affected operating systems
| Linux | debian | linux | bookworm |
| Linux | ubuntu | linux | jammy |
| Linux | ubuntu | linux | noble |
| Linux | ubuntu | linux | resolute |
| Linux | debian | linux-6.12 | bookworm |
| Linux | ubuntu | linux-aws | jammy |
| Linux | ubuntu | linux-aws | noble |
| Linux | ubuntu | linux-aws | resolute |
| Linux | ubuntu | linux-aws-5.15 | focal |
| Linux | ubuntu | linux-aws-6.8 | jammy |
| Linux | ubuntu | linux-aws-7.0 | noble |
| Linux | ubuntu | linux-aws-fips | jammy |
| Linux | ubuntu | linux-aws-fips | noble |
| Linux | ubuntu | linux-azure | jammy |
| Linux | ubuntu | linux-azure | noble |
| Linux | ubuntu | linux-azure | resolute |
| Linux | ubuntu | linux-azure-5.15 | focal |
| Linux | ubuntu | linux-azure-6.8 | jammy |
| Linux | ubuntu | linux-azure-fde | jammy |
| Linux | ubuntu | linux-azure-fde | noble |
| Linux | ubuntu | linux-azure-fde | resolute |
| Linux | ubuntu | linux-azure-fde-5.15 | focal |
| Linux | ubuntu | linux-azure-fde-6.8 | jammy |
| Linux | ubuntu | linux-azure-fde-7.0 | noble |
References & sources
- git.kernel.orgstable/c/119a2f053242ed75bdd2ebc95baf3ae7db6ccacfeuvd
- git.kernel.orgstable/c/61631352a5b405c89be579de00903b72e6888aa4euvd
- git.kernel.orgstable/c/8865cd664484517703df5c18a965dc3227572b87euvd
- git.kernel.orgstable/c/a40c45268f4358207aa9c53764fed2e05f62986aeuvd
- git.kernel.orgstable/c/889ec86464d261f026f6c334040cfc6c58c99d58euvd
- git.kernel.orgstable/c/4902a5cba21aeaf91e6b29e20e0967a5f6abdcd9euvd
- git.kernel.orgstable/c/55ee6533c1db7f7656fa8dd19637f3f8b8c08dc5euvd
- git.kernel.orgstable/c/dbd4aea175ad3c46436acb251e817b4374628072euvd
- git.kernel.orgstable/c/54b6bd40898de7906acb2bccc9a96d1b8e6b4323euvd
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: none known, automatable: no
Show the original change
Individual changes of this event as published by NVD Type Action Before After SSVC assessment added —{"id":"CVE-2026-80808","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-11-06T17:03:39.373344Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
Record modifiedLinux
1 individual change: Affected versions (publisher)
Show the original change
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/80xxx/CVE-2026-80808.json">CVE-2026-80808</a>Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
ReceivedLinux
Description added or changed
New references:- https://git.kernel.org/stable/c/119a2f053242ed75bdd2ebc95baf3ae7db6ccacf
- https://git.kernel.org/stable/c/4902a5cba21aeaf91e6b29e20e0967a5f6abdcd9
- https://git.kernel.org/stable/c/54b6bd40898de7906acb2bccc9a96d1b8e6b4323
- https://git.kernel.org/stable/c/55ee6533c1db7f7656fa8dd19637f3f8b8c08dc5
and 5 more references
Show 11 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —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.Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/80xxx/CVE-2026-80808.json">CVE-2026-80808</a>Reference added —https://git.kernel.org/stable/c/119a2f053242ed75bdd2ebc95baf3ae7db6ccacfReference added —https://git.kernel.org/stable/c/4902a5cba21aeaf91e6b29e20e0967a5f6abdcd9Reference added —https://git.kernel.org/stable/c/54b6bd40898de7906acb2bccc9a96d1b8e6b4323Reference added —https://git.kernel.org/stable/c/55ee6533c1db7f7656fa8dd19637f3f8b8c08dc5Reference added —https://git.kernel.org/stable/c/61631352a5b405c89be579de00903b72e6888aa4Reference added —https://git.kernel.org/stable/c/8865cd664484517703df5c18a965dc3227572b87Reference added —https://git.kernel.org/stable/c/889ec86464d261f026f6c334040cfc6c58c99d58Reference added —https://git.kernel.org/stable/c/a40c45268f4358207aa9c53764fed2e05f62986aReference added —https://git.kernel.org/stable/c/dbd4aea175ad3c46436acb251e817b4374628072Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-80808"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-80808.svg?lang=en" alt="CVE-2026-80808 – NEOSEC Intel" height="20"></a>