cve.bz

CVE-2026-98070 linux linux

8.1 highEPSS 0.5%Fix available

High (8.1) in linux linux. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: net/rds: acquire RDS_IN_XMIT in rds_tcp_reset_callbacks() rds_tcp_reset_callbacks() quiesces the transmit path by setting the path state to RDS_CONN_RESETTING and then waiting for RDS_IN_XMIT to be sampled clear before swapping the underlying socket and calling rds_send_path_reset(). Sampling the bit clear is not the same as owning it: rds_send_xmit() can re-acquire RDS_IN_XMIT right after the wait_event() returns. Its state recheck after taking the lock is a store-buffering pattern (the resetter writes the state and reads the bit, the sender writes the bit and reads the state) and acquire_in_xmit() is only an acquire operation, so on weakly ordered architectures both sides can miss each other's write and the transmit path then runs concurrently with rds_send_path_reset() rewriting cp_xmit_* state - which is exactly what the comment above rds_send_path_reset() tells its callers to prevent. Take the lock instead, hold it across the socket swap and rds_send_path_reset(), and release it with a wake-up at the end. The lock-ordering constraint documented above the wait still holds: the lock is acquired before lock_sock(), so a sender inside tcp_sendmsg() can never be waited on while we hold the socket lock. Two details of the old code go away with the same change: - t_sock is now read only after the lock is acquired. The old code cached it before waiting; the teardown in rds_conn_shutdown() releases that socket and clears t_sock, so a pointer cached before the wait can be stale by the time the accept path resumes. Reading it under RDS_IN_XMIT is what makes the exclusion complete once the teardown owns the same lock, which the next patch arranges; until then the teardown still only samples the bit, and the two paths remain as exposed to each other as they are today. - The old !osock early path called rds_send_path_reset() with no serialization at all. It now runs under the lock like the normal path. The conditional RDS_CONN_RESETTING transition of the previous patch happens before the socket check either way: a path found without a socket is either still connecting (its reconnect worker blocked on t_conn_path_lock) and legitimately goes RESETTING -> UP on the new socket, or it has been torn down meanwhile and is dropped. The in-function comment describing the old wait-based quiesce is rewritten to describe the lock-based one, and the stale block comment above the function (which still described a return value and an incomplete list of t_sock writers) is refreshed to name all four writers - the connect, accept, teardown and swap paths - and what serializes each of them.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 41st percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Under 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.111
  • Linux Linux: fixed in 6.18.53
  • Linux Linux: fixed in 7.2.7
  • Linux Linux: fixed in 7.3
  • Debian, Ubuntu, SUSE, openSUSE, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-98070 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-98070?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-98070?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-98070 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.

ProductAffected
Linux4.7 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.271
Linux5.155.15.222
Linux6.16.1.189
Linux6.66.6.158
Linux6.126.12.111
Linux6.186.18.53
Linux7.27.2.7
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.190-1DEBIAN-CVE-2026-98070
Debian12linux-6.126.12.111-1~deb12u1DEBIAN-CVE-2026-98070
Debian13linux6.12.111-1DEBIAN-CVE-2026-98070
Debian14linux7.2.7-1DEBIAN-CVE-2026-98070
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-98070
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-98070
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-98070
Ubuntu22.04:LTSlinux5.15.0-202.212UBUNTU-CVE-2026-98070 USN-8961-1
Ubuntu22.04:LTSlinux-aws5.15.0-1119.126UBUNTU-CVE-2026-98070 USN-8961-1
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1069.74~22.04.1UBUNTU-CVE-2026-98070 USN-9024-1
Ubuntu22.04:LTSlinux-azure5.15.0-1125.134UBUNTU-CVE-2026-98070 USN-8961-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1073.82~22.04.1UBUNTU-CVE-2026-98070 USN-9026-1
Ubuntu22.04:LTSlinux-azure-fde5.15.0-1124.133UBUNTU-CVE-2026-98070 USN-8962-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1071.78~22.04.1UBUNTU-CVE-2026-98070 USN-9026-1
Ubuntu22.04:LTSlinux-gcp5.15.0-1120.130UBUNTU-CVE-2026-98070 USN-8961-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1073.81~22.04.1UBUNTU-CVE-2026-98070 USN-9024-1
82 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 16.0kernel-default6.12.0-160000.41.1SUSE-SU-2026:24651-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-64kb, kernel-docs, kernel-syms and 6 more6.12.0-160000.41.1SUSE-SU-2026:24662-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-default-base6.12.0-160000.41.1.160000.2.32SUSE-SU-2026:24662-1
SUSELinux Enterprise Server for NVIDIA 16.1kernel-nvidia64kb, kernel-source-nvidia6.12.0-160100.7.1SUSE-SU-2026:24705-1
SUSELinux Micro 6.0kernel-default-base6.4.0-159998.55.1.159998.21.42SUSE-SU-2026:24550-1
SUSELinux Micro 6.0kernel-source, kernel-default, kernel-kvmsmall6.4.0-159998.55.1SUSE-SU-2026:24550-1
SUSELinux Micro 6.1kernel-default-base6.4.0-159998.55.1.159998.21.41SUSE-SU-2026:24619-1
SUSELinux Micro 6.1kernel-source, kernel-default, kernel-kvmsmall6.4.0-159998.55.1SUSE-SU-2026:24619-1
SUSELinux Micro 6.2kernel-default-base6.12.0-160000.41.1.160000.2.32SUSE-SU-2026:24643-1
SUSELinux Micro 6.2kernel-rt, kernel-64kb, kernel-source and 1 more6.12.0-160000.41.1SUSE-SU-2026:24643-1
SUSELinux Micro Extras 6.2kernel-syms, kernel-obs-build6.12.0-160000.41.1SUSE-SU-2026:24648-1
openSUSELeap 16.0kernel-default-base6.12.0-160000.41.1.160000.2.31openSUSE-SU-2026:22266-1
openSUSELeap 16.0kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160000.41.1openSUSE-SU-2026:22266-1
openSUSELeap 16.1kernel-default-base6.12.0-160100.9.1.160100.3.14openSUSE-SU-2026:22309-1
openSUSELeap 16.1kernel-nvidia64kb, kernel-syms-nvidia, kernel-source-nvidia6.12.0-160100.7.1openSUSE-SU-2026:22307-1
openSUSELeap 16.1kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160100.9.1openSUSE-SU-2026:22309-1
openSUSETumbleweedkernel-source7.2.9-1.1openSUSE-SU-2026:12074-1
Azure Linux3kernel6.6.158.1-1AZL-104589
Alpaquita23linux-lts6.1.189-r0BELL-CVE-2026-98070
Alpaquita25linux-lts6.12.111-r0BELL-CVE-2026-98070
Alpaquitastreamlinux-lts6.18.53-r0BELL-CVE-2026-98070

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 Moderate.

Red Hat's statement

A flaw was found in the Linux kernel's Reliable Datagram Sockets (RDS) over TCP implementation, rated Moderate by Red Hat Product Security. When an RDS-TCP connection path is reset, rds_tcp_reset_callbacks() quiesced the transmit path by waiting to sample the RDS_IN_XMIT flag clear rather than acquiring it. Because sampling the flag is not the same as owning it, and because of weak memory ordering on some architectures, the transmit path could re-acquire the flag right after the wait completed and run concurrently with rds_send_path_reset() while it rewrote the connection's transmit state. An attacker able to trigger this timing window during connection resets could cause kernel state corruption and a denial of service by crashing the system. Red Hat rates this flaw Moderate with a CVSS 3.1 score of 7.0 (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), which is lower than the CVE.org score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H); the difference reflects Red Hat's assessment of a local attack vector requiring privileges, while the CVE.org record assumes a network vector with no privileges required, and both recognize the high complexity of winning the race. In the current assessment, all maintained Red Hat products are marked not affected because the vulnerable code is not present in the shipped kernel builds; this includes RHEL 7 through RHEL 10 kernels (kernel and kernel-rt), RHEL In-Vehicle OS (In-Vehicle OS) kernels, and OpenShift RHEL CoreOS kernels. The only remaining entry, the kernel in Red Hat Enterprise Linux 6 Extended Lifecycle Support, is resolved as out of support scope (OOSS), so no fix is planned for that stream; the residual risk is limited to RHEL 6 ELS systems using RDS over TCP, which no longer receive routine security updates.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelNot affected
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Not affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Not 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-98070.

References

Check your stackJSON