CVE-2026-97918 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.6.160
- Linux Linux: fixed in 6.12.112
- 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-97918 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-97918?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-97918?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-97918 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 | 4.17 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.6 | 6.6.160 |
| Linux | 6.12 | 6.12.112 |
| 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 | no fix listed | DEBIAN-CVE-2026-97918 |
| Debian | 12 | linux-6.12 | 6.12.113-1~deb12u1 | DEBIAN-CVE-2026-97918 |
| Debian | 13 | linux | 6.12.113-1 | DEBIAN-CVE-2026-97918 |
| Debian | 14 | linux | 7.2.7-1 | DEBIAN-CVE-2026-97918 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-97918 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-97918 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-97918 |
| Ubuntu | 22.04:LTS | linux, linux-aws, linux-gcp and 48 more | no fix listed | UBUNTU-CVE-2026-97918 |
| Ubuntu | 22.04:LTS | linux-aws-6.8 | 6.8.0-1069.74~22.04.1 | UBUNTU-CVE-2026-97918 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-azure-6.8 | 6.8.0-1073.82~22.04.1 | UBUNTU-CVE-2026-97918 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1071.78~22.04.1 | UBUNTU-CVE-2026-97918 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-gcp-6.8 | 6.8.0-1073.81~22.04.1 | UBUNTU-CVE-2026-97918 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-hwe-6.8 | 6.8.0-149.149~22.04.1 | UBUNTU-CVE-2026-97918 USN-9066-1 |
| Ubuntu | 22.04:LTS | linux-ibm-6.8 | 6.8.0-1069.70~22.04.1 | UBUNTU-CVE-2026-97918 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-149.149.1~22.04.1 | UBUNTU-CVE-2026-97918 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-oracle-6.8 | 6.8.0-1067.71~22.04.1 | UBUNTU-CVE-2026-97918 USN-9025-1 |
| 48 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.161.1-1 | AZL-104526 |
| Alpaquita | 23 | linux-lts | no fix listed | BELL-CVE-2026-97918 |
| Alpaquita | 25 | linux-lts | 6.12.112-r0 | BELL-CVE-2026-97918 |
| Alpaquita | stream | linux-lts | 6.18.53-r0 | BELL-CVE-2026-97918 |
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 use-after-free flaw was found in the Linux kernel's tracing subsystem histogram trigger implementation (kernel/trace/trace_events_hist.c), which Red Hat rates as Moderate impact. When enabling a histogram event trigger fails, the error path removes the trigger from the per-file trigger list before the normal unregistration processing runs, so the cleanup code cannot find it and skips removing its entry from the global named_triggers list; the trigger is then freed while still referenced there. Subsequent trigger operations, such as find_named_trigger(), can dereference that freed memory (KASAN reports a slab-use-after-free read), most likely crashing the kernel and causing a denial of service. Exploiting this flaw requires local access with the privileges needed to configure event tracing through tracefs, typically root or CAP_SYS_ADMIN. Because the confirmed impact is a read of freed memory by an already-privileged local user and no arbitrary memory write has been demonstrated, Red Hat assesses this as a denial-of-service issue (CVSS 3.1 score 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), lower in practical severity than the upstream description's mention of potential privilege escalation. Red Hat Enterprise Linux 6 and 7 are not affected because the vulnerable code is not present in those releases. For the affected Red Hat Enterprise Linux 8, 9, and 10, Red Hat In-Vehicle OS, and OpenShift Container Platform (RHEL CoreOS) streams, the fix is deferred: since only users who already hold administrative privileges on the system can trigger the flaw and the primary consequence is a kernel crash, the fix will be delivered in a future scheduled update rather than an immediate erratum. The residual risk is therefore limited to denial of service by an already-privileged local user.
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 | 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 | 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-97918.
References
- https://git.kernel.org/stable/c/51b07104d563d4be2be34158d3b9d922ca417642
- https://git.kernel.org/stable/c/880712b6f48103ba3a04b154ff076d45fe86dcec
- https://git.kernel.org/stable/c/92383cef66791a0c63a2f27755cadbdb2fbf270b
- https://git.kernel.org/stable/c/bfa6bc11aef93a3d9db0ac9564b734849a9d959b
- https://git.kernel.org/stable/c/c7ee2d5733574d4694f7c0035e4381f54c1fca27