CVE-2026-98399 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; 10th 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.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, Alpaquita: fixed package versions per release
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-98399 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-98399?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-98399?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-98399 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 | 2.6.30 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| 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 | no fix listed | DEBIAN-CVE-2026-98399 |
| Debian | 13 | linux | 6.12.111-1 | DEBIAN-CVE-2026-98399 |
| Debian | 14 | linux | 7.2.7-1 | DEBIAN-CVE-2026-98399 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-98399 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-98399 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-98399 |
| Ubuntu | 22.04:LTS | linux, linux-aws, linux-gcp and 48 more | no fix listed | UBUNTU-CVE-2026-98399 |
| Ubuntu | 22.04:LTS | linux-aws-6.8 | 6.8.0-1069.74~22.04.1 | UBUNTU-CVE-2026-98399 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-azure-6.8 | 6.8.0-1073.82~22.04.1 | UBUNTU-CVE-2026-98399 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1071.78~22.04.1 | UBUNTU-CVE-2026-98399 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-gcp-6.8 | 6.8.0-1073.81~22.04.1 | UBUNTU-CVE-2026-98399 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-hwe-6.8 | 6.8.0-149.149~22.04.1 | UBUNTU-CVE-2026-98399 USN-9066-1 |
| Ubuntu | 22.04:LTS | linux-ibm-6.8 | 6.8.0-1069.70~22.04.1 | UBUNTU-CVE-2026-98399 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-149.149.1~22.04.1 | UBUNTU-CVE-2026-98399 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-oracle-6.8 | 6.8.0-1067.71~22.04.1 | UBUNTU-CVE-2026-98399 USN-9025-1 |
| 50 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| Azure Linux | 3 | kernel | no fix listed | AZL-108129 |
| Alpaquita | 23 | linux-lts | no fix listed | BELL-CVE-2026-98399 |
| Alpaquita | 25 | linux-lts | 6.12.111-r0 | BELL-CVE-2026-98399 |
| Alpaquita | stream | linux-lts | 6.18.53-r0 | BELL-CVE-2026-98399 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 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 · Alpaquita.
Red Hat
Red Hat rates this Low.
A low severity flaw was found in the Linux kernel s390 (IBM Z) IPL subsystem. On systems booted without an IPL parameter block, such as via HMC FTP boot or QEMU direct kernel boot, reipl_type_init() selects IPL_TYPE_UNKNOWN and reipl_block_actual remains NULL, yet dump_reipl_run() unconditionally dereferences that pointer while preparing the lowcore fields for a stand-alone dump. A local privileged user who triggers a stand-alone dump on such a system can cause a NULL pointer dereference and kernel crash, resulting in a denial of service; alternatively, when address zero happens to contain readable lowcore data, the stand-alone dumper completes the dump and enters disabled wait, preventing the expected automatic re-IPL. Only availability is impacted; there is no effect on confidentiality or integrity. Red Hat Enterprise Linux 6 is an out-of-support stream (OOSS), while the kernel and kernel-rt packages in Red Hat Enterprise Linux 7, 8, 9, and 10, Red Hat In-Vehicle OS, and the OpenShift Container Platform RHEL CoreOS kernels are affected with fixes currently deferred: triggering the flaw requires local administrative privileges on an s390 system booted in an uncommon configuration, and the residual risk is limited to a denial of service during stand-alone dump or shutdown workflows. Red Hat assesses this issue as LOW severity, lower than the upstream rating, because exploitation requires local privileged access and an uncommon s390 boot configuration, and the impact is confined to availability.
On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time.
| 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 | Fix deferred | |
| Red Hat Enterprise Linux 7 | kernel-rt | Fix deferred | |
| 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-98399.
References
- https://git.kernel.org/stable/c/280ff19853440d59e031cd8fe161e81305721262
- https://git.kernel.org/stable/c/37f61b71cbc0caefc01022a19ee56fc2510e2e6e
- https://git.kernel.org/stable/c/41647864e62b28388ecccc23a82f0e0a091f4ef2
- https://git.kernel.org/stable/c/8d7988e8116c3d29d9e02ca9d37ee84577643f2d
- https://git.kernel.org/stable/c/aed56fa3108b7095e6a048e134981506c056a6cb