CVE-2026-80760 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, SUSE, openSUSE, Alpaquita: fixed package versions per release
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-80760 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-80760?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-80760?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-80760 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.13 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-80760 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-80760 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-80760 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-80760 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 more | no fix listed | UBUNTU-CVE-2026-80760 |
| Ubuntu | 24.04:LTS | linux-aws-7.0 | 7.0.0-1017.18~24.04.1 | UBUNTU-CVE-2026-80760 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-azure-fde-7.0 | 7.0.0-1019.19~24.04.1 | UBUNTU-CVE-2026-80760 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-gcp-7.0 | 7.0.0-1017.19~24.04.1 | UBUNTU-CVE-2026-80760 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-hwe-7.0 | 7.0.0-42.42~24.04.1 | UBUNTU-CVE-2026-80760 USN-8959-1 |
| Ubuntu | 24.04:LTS | linux-oracle-7.0 | 7.0.0-1016.18~24.04.1 | UBUNTU-CVE-2026-80760 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-80760 |
| Ubuntu | 24.04:LTS | linux-riscv-7.0 | 7.0.0-42.42.1~24.04.1 | UBUNTU-CVE-2026-80760 |
| Ubuntu | 26.04:LTS | linux | 7.0.0-42.42 | UBUNTU-CVE-2026-80760 USN-8959-1 |
| 12 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| SUSE | Linux Enterprise High Availability Extension 16.0 | kernel-default | 6.12.0-160000.41.1 | SUSE-SU-2026:24651-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | kernel-64kb, kernel-docs, kernel-syms and 6 more | 6.12.0-160000.41.1 | SUSE-SU-2026:24662-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | kernel-default-base | 6.12.0-160000.41.1.160000.2.32 | SUSE-SU-2026:24662-1 |
| SUSE | Linux Enterprise Server for NVIDIA 16.1 | kernel-nvidia64kb, kernel-source-nvidia | 6.12.0-160100.7.1 | SUSE-SU-2026:24705-1 |
| SUSE | Linux Micro 6.2 | kernel-default-base | 6.12.0-160000.41.1.160000.2.32 | SUSE-SU-2026:24643-1 |
| SUSE | Linux Micro 6.2 | kernel-rt, kernel-64kb, kernel-source and 1 more | 6.12.0-160000.41.1 | SUSE-SU-2026:24643-1 |
| SUSE | Linux Micro Extras 6.2 | kernel-syms, kernel-obs-build | 6.12.0-160000.41.1 | SUSE-SU-2026:24648-1 |
| openSUSE | Leap 16.0 | kernel-default-base | 6.12.0-160000.41.1.160000.2.31 | openSUSE-SU-2026:22266-1 |
| openSUSE | Leap 16.0 | kernel-rt, dtb-aarch64, kernel-64kb and 9 more | 6.12.0-160000.41.1 | openSUSE-SU-2026:22266-1 |
| openSUSE | Leap 16.1 | kernel-default-base | 6.12.0-160100.9.1.160100.3.14 | openSUSE-SU-2026:22309-1 |
| openSUSE | Leap 16.1 | kernel-nvidia64kb, kernel-syms-nvidia, kernel-source-nvidia | 6.12.0-160100.7.1 | openSUSE-SU-2026:22307-1 |
| openSUSE | Leap 16.1 | kernel-rt, dtb-aarch64, kernel-64kb and 9 more | 6.12.0-160100.9.1 | openSUSE-SU-2026:22309-1 |
| 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-80760 |
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 · SUSE · openSUSE · Alpaquita.
Red Hat
Red Hat rates this Moderate.
Bluetooth MGMT HCI_CMD_SYNC accepted a params_len value that fits the management message but does not fit the u8 parameter length field in the HCI command header. A local actor with access to the Bluetooth management interface could set params_len to more than 255, causing the header length to be truncated while the full parameter bytes are still appended to the outgoing frame. On length framed transports such as H:4, the controller may treat the trailing bytes as the start of another HCI packet, causing command stream desynchronization, unintended controller behavior, or denial of service. For the CVSS the PR:L is used for the paranoid score because reduced capability root, a service account, or delegated Bluetooth management access may be enough in some deployments. The issue is not directly network reachable from a remote Bluetooth peer and does not show a kernel memory corruption primitive.
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
| 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 | Fix deferred | |
| 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 | Fix deferred | |
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-9 | Fix deferred |
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-80760.