CVE-2026-98322 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; 8th 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 5.10.271
- Linux Linux: fixed in 5.15.222
- Linux Linux: fixed in 6.1.189
- Linux Linux: fixed in 6.6.158
- Linux Linux: fixed in 6.12.112
- Linux Linux: fixed in 6.18.54
- Linux Linux: fixed in 7.2.8
- 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-98322 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-98322?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-98322?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-98322 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.8 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 5.10 | 5.10.271 |
| Linux | 5.15 | 5.15.222 |
| Linux | 6.1 | 6.1.189 |
| Linux | 6.6 | 6.6.158 |
| Linux | 6.12 | 6.12.112 |
| Linux | 6.18 | 6.18.54 |
| Linux | 7.2 | 7.2.8 |
| Linux | later releases | 7.3 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | linux | 6.1.190-1 | DEBIAN-CVE-2026-98322 |
| Debian | 12 | linux-6.12 | 6.12.113-1~deb12u1 | DEBIAN-CVE-2026-98322 |
| Debian | 13 | linux | 6.12.113-1 | DEBIAN-CVE-2026-98322 |
| Debian | 14 | linux | 7.2.8-1 | DEBIAN-CVE-2026-98322 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-98322 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-98322 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-98322 |
| Ubuntu | 22.04:LTS | linux | 5.15.0-202.212 | UBUNTU-CVE-2026-98322 USN-8961-1 |
| Ubuntu | 22.04:LTS | linux-aws | 5.15.0-1119.126 | UBUNTU-CVE-2026-98322 USN-8961-1 |
| Ubuntu | 22.04:LTS | linux-aws-6.8 | 6.8.0-1069.74~22.04.1 | UBUNTU-CVE-2026-98322 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-azure | 5.15.0-1125.134 | UBUNTU-CVE-2026-98322 USN-8961-1 |
| Ubuntu | 22.04:LTS | linux-azure-6.8 | 6.8.0-1073.82~22.04.1 | UBUNTU-CVE-2026-98322 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-azure-fde | 5.15.0-1124.133 | UBUNTU-CVE-2026-98322 |
| Ubuntu | 22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1071.78~22.04.1 | UBUNTU-CVE-2026-98322 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-gcp | 5.15.0-1120.130 | UBUNTU-CVE-2026-98322 USN-8961-1 |
| Ubuntu | 22.04:LTS | linux-gcp-6.8 | 6.8.0-1073.81~22.04.1 | UBUNTU-CVE-2026-98322 USN-9024-1 |
| 78 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| openSUSE | Tumbleweed | kernel-source | 7.2.10-1.1 | openSUSE-SU-2026:12131-1 |
| Azure Linux | 3 | kernel | 6.6.158.1-1 | AZL-106158 |
| Alpaquita | 23 | linux-lts | 6.1.189-r0 | BELL-CVE-2026-98322 |
| Alpaquita | 25 | linux-lts | 6.12.112-r0 | BELL-CVE-2026-98322 |
| Alpaquita | stream | linux-lts | 6.18.55-r0 | BELL-CVE-2026-98322 |
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 flaw rated Moderate impact affects the Linux kernel's netfilter nftables NAT implementation in Red Hat Enterprise Linux 9 and 10, Red Hat In-Vehicle OS, and OpenShift Container Platform releases built on RHEL CoreOS 9. When an IPv4 NAT rule using the nftables netmap feature is configured, nft_nat_setup_netmap() writes only the 4-byte IPv4 member of the 16-byte on-stack union nf_inet_addr before copying the whole union into the NAT range, so up to 12 bytes of uninitialized kernel stack data reach nf_nat_setup_info() and are processed during packet evaluation. A local user with the network administration privileges (CAP_NET_ADMIN) needed to configure nftables rules could exploit this flaw to cause a denial of service, and the processed uninitialized stack data could potentially expose limited kernel memory, although no information disclosure has been demonstrated. The IPv6 netmap path initializes all 16 bytes of the union and is not affected. Red Hat Enterprise Linux 6, 7, and 8, and OpenShift Container Platform releases built on RHEL CoreOS 8, are not affected because the vulnerable code is not present in those releases. For the affected products, the fix is currently deferred: given the moderate impact of the flaw and the requirement for local administrative privileges to trigger it, a fix is not planned for these releases at this time. The residual risk is that systems using IPv4 netmap NAT rules may experience a denial of service or, at most, limited exposure of uninitialized kernel stack data.
This flaw is only reachable through nftables IPv4 NAT rules that use the netmap feature. Avoiding the netmap option when configuring IPv4 NAT rules, and using explicit address ranges for the required translations instead, avoids the affected code path. For deployments where this is not practical, 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 | 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-98322.
References
- https://git.kernel.org/stable/c/0ce42c7b84032335abff9eac43762e4ca8224451
- https://git.kernel.org/stable/c/161f5860c92a8ec80b6bdff16e79d70dcd8afc5a
- https://git.kernel.org/stable/c/1c43f5db482f74b41987c39c9c375a5e767556eb
- https://git.kernel.org/stable/c/29365695842db0a97b701a43a09fad1b4f7ecf3e
- https://git.kernel.org/stable/c/7b9380c38c2fd2189416fa602bdbc5c8523b84b2
- https://git.kernel.org/stable/c/d313499df66159b4b7971d760d16729598ab7e5a
- https://git.kernel.org/stable/c/e4982c489ee359162eee3ece1fb36082648464a5
- https://git.kernel.org/stable/c/eb2030137dba3b59cbb5057a33af70488d6bc231