CVE-2026-80810 linux linux
linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
On this page
- EPSS
- 0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 11th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
- Published
- Modified
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Fix and patched versions
- Linux Linux: fixed in 6.18.47
- Linux Linux: fixed in 7.1.11
- Linux Linux: fixed in 7.2.1
- Linux Linux: fixed in 7.3
- Debian, Ubuntu, openSUSE, Alpaquita: fixed package versions per release
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-80810 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-80810?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-80810?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-80810 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | 6.15 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.18 | 6.18.47 |
| Linux | 7.1 | 7.1.11 |
| Linux | 7.2 | 7.2.1 |
| Linux | later releases | 7.3 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 14 | linux | 7.1.12-1 | DEBIAN-CVE-2026-80810 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-80810 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-80810 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-80810 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 more | no fix listed | UBUNTU-CVE-2026-80810 |
| Ubuntu | 24.04:LTS | linux-aws-7.0 | 7.0.0-1017.18~24.04.1 | UBUNTU-CVE-2026-80810 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-azure-fde-7.0 | 7.0.0-1019.19~24.04.1 | UBUNTU-CVE-2026-80810 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-gcp-7.0 | 7.0.0-1017.19~24.04.1 | UBUNTU-CVE-2026-80810 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-hwe-7.0 | 7.0.0-42.42~24.04.1 | UBUNTU-CVE-2026-80810 USN-8959-1 |
| Ubuntu | 24.04:LTS | linux-oracle-7.0 | 7.0.0-1016.18~24.04.1 | UBUNTU-CVE-2026-80810 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-riscv, linux-oem-6.8, linux-aws-6.14 and 27 more | no fix listed | UBUNTU-CVE-2026-80810 |
| Ubuntu | 24.04:LTS | linux-riscv-7.0 | 7.0.0-42.42.1~24.04.1 | UBUNTU-CVE-2026-80810 |
| Ubuntu | 26.04:LTS | linux | 7.0.0-42.42 | UBUNTU-CVE-2026-80810 USN-8959-1 |
| 12 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| openSUSE | Tumbleweed | kernel-source | 7.2.5-1.1 | openSUSE-SU-2026:11773-1 |
| Alpaquita | stream | linux-lts | 6.18.53-r0 | BELL-CVE-2026-80810 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpaquita.
Red Hat
Red Hat rates this Important.
This vulnerability is rated as an Important severity flaw because a local unprivileged attacker could potentially achieve kernel memory corruption, leading to system crashes or local privilege escalation, although exploitation requires highly specific hardware and memory configurations. The defect only triggers on architectures that support gigantic hugetlb folio allocations—specifically 64KB-page ARM64 and PowerPC architectures with multi-gigabyte page sizes—and does not affect standard x86_64 deployments where maximum page shifts remain bounded. Furthermore, the vulnerable code path was introduced in newer kernel releases and is not present in Red Hat Enterprise Linux 7, 8, or 9.
Disable io_uring system-wide using sysctl to prevent creation and registration of io_uring buffers.
To apply this change immediately on running systems:
```sh
sysctl -w kernel.io_uring_disabled=2
```
To persist this setting across system boots:
```sh
echo "kernel.io_uring_disabled = 2" > /etc/sysctl.d/99-disable-io-uring.conf
```
Caveats:
Disabling io_uring will cause services and applications that depend on io_uring asynchronous I/O to fail or fall back to synchronous operations. Active processes with existing io_uring instances must be restarted for the restriction to take full effect. Systems running on x86_64 are not exposed, and on vulnerable architectures, avoiding the allocation of 16GB gigantic hugetlb pages also prevents exposure.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 6 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Not affected | |
| Red Hat Enterprise Linux 8 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 9 | kernel | Not affected | |
| Red Hat Enterprise Linux 9 | kernel-rt | Not affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-8 | Not affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-9 | Not affected | |
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-9 | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-80810.