CVE-2026-98178 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; 5th 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 7.2.8
- Linux Linux: fixed in 7.3
- Debian, openSUSE: fixed package versions per release
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-98178 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-98178?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-98178?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-98178 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 | 7.2 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 7.2 | 7.2.8 |
| Linux | later releases | 7.3 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 14 | linux | 7.2.8-1 | DEBIAN-CVE-2026-98178 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-98178 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-98178 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-98178 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 more | no fix listed | UBUNTU-CVE-2026-98178 |
| Ubuntu | 24.04:LTS | linux-riscv, linux-oem-6.8, linux-aws-6.14 and 23 more | no fix listed | UBUNTU-CVE-2026-98178 |
| Ubuntu | Pro:Realtime:24.04:LTS | linux-realtime-6.14, linux-realtime-6.17 | no fix listed | UBUNTU-CVE-2026-98178 |
| openSUSE | Tumbleweed | kernel-source | 7.2.10-1.1 | openSUSE-SU-2026:12131-1 |
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. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.
Red Hat
Red Hat rates this Low.
A low impact vulnerability was found in the Linux kernel's AMD GPU driver (drm/amdgpu). The amdgpu_amdkfd_clear_kfd_mapping() function assumed that an attached KFD (compute) device always had a fully populated node array. When KFD device initialization failed after GPU probe, for example on Polaris hardware without the required PCIe atomics support, the kfd_dev structure remained attached to the amdgpu device even though its nodes had not been allocated. A local user able to trigger a subsequent GPU reset could cause the kernel to dereference an unallocated pointer (nodes[0]), resulting in a kernel crash and denial of service. Red Hat Product Security rates this flaw as low impact (CVSS 3.1: 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) because exploitation requires local access with privileges and specific affected hardware configurations where KFD initialization fails. All maintained Red Hat Enterprise Linux kernel and kernel-rt update streams are not affected by this flaw because the vulnerable code is not present; only the Red Hat Enterprise Linux 6 Extended Lifecycle Support (rhel-6-els) stream, which is out of support scope, remains affected-status pending for this issue.
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 | Not affected | |
| 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 | 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-98178.