CVE-2026-97424 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 6.6.160
- Linux Linux: fixed in 6.12.114
- Linux Linux: fixed in 6.18.53
- Linux Linux: fixed in 7.2
- Debian, Ubuntu, SUSE, openSUSE, Azure Linux, Alpaquita: fixed package versions per release
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-97424 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-97424?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-97424?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-97424 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 | 5.2 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.6 | 6.6.160 |
| Linux | 6.12 | 6.12.114 |
| Linux | 6.18 | 6.18.53 |
| Linux | later releases | 7.2 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | linux | no fix listed | DEBIAN-CVE-2026-97424 |
| Debian | 12 | linux-6.12 | 6.12.115-2~deb12u1 | DEBIAN-CVE-2026-97424 |
| Debian | 13 | linux | 6.12.115-2 | DEBIAN-CVE-2026-97424 |
| Debian | 14 | linux | 7.2.6-1 | DEBIAN-CVE-2026-97424 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-97424 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-97424 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-97424 |
| Ubuntu | 22.04:LTS | linux, linux-aws, linux-gcp and 57 more | no fix listed | UBUNTU-CVE-2026-97424 |
| Ubuntu | 24.04:LTS | linux, linux-aws, linux-gcp and 44 more | no fix listed | UBUNTU-CVE-2026-97424 |
| Ubuntu | 24.04:LTS | linux-aws-7.0 | 7.0.0-1017.18~24.04.1 | UBUNTU-CVE-2026-97424 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-azure-fde-7.0 | 7.0.0-1019.19~24.04.1 | UBUNTU-CVE-2026-97424 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-gcp-7.0 | 7.0.0-1017.19~24.04.1 | UBUNTU-CVE-2026-97424 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-hwe-7.0 | 7.0.0-42.42~24.04.1 | UBUNTU-CVE-2026-97424 USN-8959-1 |
| Ubuntu | 24.04:LTS | linux-oracle-7.0 | 7.0.0-1016.18~24.04.1 | UBUNTU-CVE-2026-97424 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-riscv-7.0 | 7.0.0-42.42.1~24.04.1 | UBUNTU-CVE-2026-97424 |
| Ubuntu | 26.04:LTS | linux | 7.0.0-42.42 | UBUNTU-CVE-2026-97424 USN-8959-1 |
| 20 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| SUSE | Linux Enterprise Server for NVIDIA 16.1 | kernel-nvidia64kb, kernel-source-nvidia | 6.12.0-160100.7.1 | SUSE-SU-2026:24705-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 |
| Azure Linux | 3 | kernel | 6.6.161.1-1 | AZL-103700 |
| Alpaquita | 23 | linux-lts | no fix listed | BELL-CVE-2026-97424 |
| Alpaquita | 25 | linux-lts | 6.12.115-r0 | BELL-CVE-2026-97424 |
| Alpaquita | stream | linux-lts | 6.18.53-r0 | BELL-CVE-2026-97424 |
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 · SUSE · openSUSE · Alpaquita.
Red Hat
Red Hat rates this Low.
A flaw of low impact was found in the Linux kernel's AMD GPU (amdgpu) driver as shipped in Red Hat Enterprise Linux 9 and 10, Red Hat In-Vehicle OS 2, and OpenShift Container Platform releases built on RHEL 9 CoreOS. The issue is in the Reliability, Availability, and Serviceability (RAS) handling of the cp_ecc_error_irq interrupt: the interrupt is acquired during RAS late initialization but released from a separate hardware shutdown path, and the RAS teardown has no suspend counterpart. As a result, a local user able to trigger a system suspend followed by unloading the amdgpu driver without an intervening resume can cause the same interrupt resources to be released twice. This double-release can destabilize the system and lead to a kernel crash (denial of service). There is no impact on confidentiality or integrity.
Red Hat Enterprise Linux 7 and 8, including their realtime kernels, and OpenShift Container Platform 4.12 built on RHEL 8 CoreOS are not affected because the vulnerable code is not present in those releases.
Fixes for the affected products are currently deferred because the security risk is low: triggering the flaw requires local access with the ability to trigger a system suspend and unload the amdgpu driver, and the consequence is limited to loss of system availability. The residual risk on systems with affected AMD GPUs is a kernel crash or loss of GPU availability when the suspend-then-unload sequence occurs. Although the CVSS 3.1 base score is 5.5 (Moderate), the overall Red Hat severity is Low due to the local privileged access required and the availability-only impact.
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 | 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 | Fix deferred | |
| 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-97424.