CVE-2026-98475 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) estimated probability of exploitation activity in the next 30 days; 6th 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.12.112
- Linux Linux: fixed in 6.18.55
- Linux Linux: fixed in 7.2.9
- Linux Linux: fixed in 7.3
- Debian, Ubuntu, Alpaquita: fixed package versions per release
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-98475 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-98475?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-98475?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-98475 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.9 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.12 | 6.12.112 |
| Linux | 6.18 | 6.18.55 |
| Linux | 7.2 | 7.2.9 |
| Linux | later releases | 7.3 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | linux-6.12 | 6.12.113-1~deb12u1 | DEBIAN-CVE-2026-98475 |
| Debian | 13 | linux | 6.12.113-1 | DEBIAN-CVE-2026-98475 |
| Debian | 14 | linux | 7.2.9-1 | DEBIAN-CVE-2026-98475 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-98475 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-98475 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-98475 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 more | no fix listed | UBUNTU-CVE-2026-98475 |
| Ubuntu | 24.04:LTS | linux-aws-7.0 | 7.0.0-1017.18~24.04.1 | UBUNTU-CVE-2026-98475 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-azure-fde-7.0 | 7.0.0-1019.19~24.04.1 | UBUNTU-CVE-2026-98475 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-gcp-7.0 | 7.0.0-1017.19~24.04.1 | UBUNTU-CVE-2026-98475 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-hwe-7.0 | 7.0.0-42.42~24.04.1 | UBUNTU-CVE-2026-98475 USN-8959-1 |
| Ubuntu | 24.04:LTS | linux-oracle-7.0 | 7.0.0-1016.18~24.04.1 | UBUNTU-CVE-2026-98475 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-98475 |
| Ubuntu | 24.04:LTS | linux-riscv-7.0 | 7.0.0-42.42.1~24.04.1 | UBUNTU-CVE-2026-98475 |
| Ubuntu | 26.04:LTS | linux | 7.0.0-42.42 | UBUNTU-CVE-2026-98475 USN-8959-1 |
| 12 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| Alpaquita | 25 | linux-lts | 6.12.112-r0 | BELL-CVE-2026-98475 |
| Alpaquita | stream | linux-lts | 6.18.55-r0 | BELL-CVE-2026-98475 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.
Red Hat
Red Hat rates this Moderate.
An address space confusion in s390 channel measurement handling can pass a virtual measurement block address to firmware as an absolute DMA address. On kernels built with CONFIG_RANDOMIZE_IDENTITY_BASE, firmware may therefore store extended channel measurement data at an unintended physical address. Depending on firmware address validation and the resulting location, this may cause measurement failure, corruption of unrelated physical memory, a kernel crash, or loss of system availability. The issue is local, specific to affected s390 configurations, and is not directly network reachable. For the CVSS the PR:H is selected because activating or configuring channel measurement blocks normally requires administrative control over the channel subsystem. The base score represents limited integrity impact and high availability impact from a wrong firmware write. The paranoid score treats the unintended physical memory write as a potential strong kernel memory corruption primitive, although reliable attacker control over the destination and contents is not established.
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-98475.