CVE-2026-97995 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; 7th 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 5.10.271
- Linux Linux: fixed in 5.15.222
- Linux Linux: fixed in 6.1.189
- Linux Linux: fixed in 6.6.158
- Linux Linux: fixed in 6.12.111
- Linux Linux: fixed in 6.18.53
- Linux Linux: fixed in 7.2.7
- Linux Linux: fixed in 7.3
- Debian, Ubuntu, openSUSE, Azure Linux, Alpaquita: fixed package versions per release
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-97995 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-97995?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-97995?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-97995 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 | from 3.16.60 before 3.17 |
| Linux | from 3.18.108 before 3.19 |
| Linux | from 4.1.52 before 4.2 |
| Linux | from 4.4.131 before 4.5 |
| Linux | from 4.9.98 before 4.10 |
| Linux | from 4.14.39 before 4.15 |
| Linux | from 4.16.7 before 4.17 |
| Linux | 4.17 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 5.10 | 5.10.271 |
| Linux | 5.15 | 5.15.222 |
| Linux | 6.1 | 6.1.189 |
| Linux | 6.6 | 6.6.158 |
| Linux | 6.12 | 6.12.111 |
| Linux | 6.18 | 6.18.53 |
| Linux | 7.2 | 7.2.7 |
| Linux | later releases | 7.3 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | linux | 6.1.190-1 | DEBIAN-CVE-2026-97995 |
| Debian | 12 | linux-6.12 | 6.12.111-1~deb12u1 | DEBIAN-CVE-2026-97995 |
| Debian | 13 | linux | 6.12.111-1 | DEBIAN-CVE-2026-97995 |
| Debian | 14 | linux | 7.2.7-1 | DEBIAN-CVE-2026-97995 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-97995 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-97995 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-97995 |
| Ubuntu | 22.04:LTS | linux | 5.15.0-202.212 | UBUNTU-CVE-2026-97995 USN-8961-1 |
| Ubuntu | 22.04:LTS | linux-aws | 5.15.0-1119.126 | UBUNTU-CVE-2026-97995 USN-8961-1 |
| Ubuntu | 22.04:LTS | linux-aws-6.8 | 6.8.0-1069.74~22.04.1 | UBUNTU-CVE-2026-97995 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-azure | 5.15.0-1125.134 | UBUNTU-CVE-2026-97995 USN-8961-1 |
| Ubuntu | 22.04:LTS | linux-azure-6.8 | 6.8.0-1073.82~22.04.1 | UBUNTU-CVE-2026-97995 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-azure-fde | 5.15.0-1124.133 | UBUNTU-CVE-2026-97995 USN-8962-1 |
| Ubuntu | 22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1071.78~22.04.1 | UBUNTU-CVE-2026-97995 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-gcp | 5.15.0-1120.130 | UBUNTU-CVE-2026-97995 USN-8961-1 |
| Ubuntu | 22.04:LTS | linux-gcp-6.8 | 6.8.0-1073.81~22.04.1 | UBUNTU-CVE-2026-97995 USN-9024-1 |
| 82 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| openSUSE | Tumbleweed | kernel-source | 7.2.9-1.1 | openSUSE-SU-2026:12074-1 |
| Azure Linux | 3 | kernel | 6.6.158.1-1 | AZL-104289 |
| Alpaquita | 23 | linux-lts | 6.1.189-r0 | BELL-CVE-2026-97995 |
| Alpaquita | 25 | linux-lts | 6.12.111-r0 | BELL-CVE-2026-97995 |
| Alpaquita | stream | linux-lts | 6.18.53-r0 | BELL-CVE-2026-97995 |
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; Microsoft's Azure Linux vulnerability data, MIT; 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 Moderate.
A moderate-impact flaw was found in the Linux kernel virtio_console driver. When a virtio console device is unbound or removed while a control message is still queued on the control-out virtqueue, remove_vqs() passes the leftover cookie (which points into the ports_device structure, &portdev->cpkt) to free_buf(), which misinterprets it as a struct port_buffer and reads past the end of the ports_device allocation, resulting in a slab out-of-bounds read (reported by KASAN). Exploiting this requires local access with administrative privileges (for example, unbinding the device via sysfs) and a control message in flight on the control-out queue at the moment of removal, so the practical attack surface is narrow. The primary consequence is a kernel crash and denial of service; although the CVE description notes potential exposure of sensitive kernel memory, the Red Hat assessment (CVSS 3.1 score 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) rates confidentiality as not impacted because the out-of-bounds read occurs internally during device teardown. Red Hat Enterprise Linux 7 Extended Lifecycle Support streams are not affected because the vulnerable code is not present in those kernels. The affected Red Hat Enterprise Linux 8, 9, and 10, Red Hat In-Vehicle OS, and OpenShift (RHEL CoreOS) kernel streams are currently marked for deferred fixes, given that triggering the flaw requires privileged local access and a race during device teardown; the residual risk is that such a privileged local user could crash the system.
Mitigation for this issue is either not available or the currently available options do not 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 | Out of support scope | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 8 | kernel-rt | Fix deferred | |
| Red Hat Enterprise Linux 9 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 9 | kernel-rt | Fix deferred | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-8 | Fix deferred | |
| 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-97995.
References
- https://git.kernel.org/stable/c/177ee901aa2bab02e7f1f8edbb814fd5e386ed62
- https://git.kernel.org/stable/c/2e40c69b9c3448b9c6609cd02013da593b2e123b
- https://git.kernel.org/stable/c/894f98e73983f37354214a89a3a7fd35bf9e3072
- https://git.kernel.org/stable/c/8f6cfc3eca79b8e108d0823756101e2f4f9d811f
- https://git.kernel.org/stable/c/a80c33488e0bbe642ed803b13a4ac8078a70b507
- https://git.kernel.org/stable/c/b1f39c2a676698cc64c8e105e08b25111a112ec6
- https://git.kernel.org/stable/c/e03522a990cd2e0f1a736eaa349a9df9ab8541c3
- https://git.kernel.org/stable/c/f620c40ea6862feed84deb105568b21ec53a7830