CVE-2026-98068

A flaw was found in the Linux kernel's Reliable Datagram Sockets (RDS) subsystem. A race condition during connection shutdown can lead to a Denial of Service (DoS). When connection teardown coincides with a concurrent connection drop or incoming connection, the kernel may fail to complete socket cleanup. Consequently, the connection becomes wedged in an unresponsive state, exhausting resources and halting network communication.

A moderate-impact flaw was found in the Linux kernel's Reliable Datagram Sockets (RDS) subsystem. A race condition in rds_conn_shutdown() allows the final shutdown state transition to consume an RDS_CONN_ERROR state set by a concurrent connection drop (for example, a FIN processed in softirq context or an administrative reset) racing with teardown or with an incoming connection accepted by rds_tcp_accept_one(). When this happens, the cleanup pass queued by the drop becomes a no-op, so a newly accepted socket can remain established with its callbacks armed while the connection path is wedged in RDS_CONN_DOWN. The socket's receive queue then grows without bound and the peer's send path stalls behind it, resulting in a denial of service. During network namespace teardown or module unload, the same race can leave a reconnect timer armed on a connection path that is subsequently freed, potentially causing a kernel panic. Exploitation depends on winning a narrow timing window between concurrent connection state transitions, which is reflected in the moderate impact rating. No shipped Red Hat product is currently affected: Red Hat Enterprise Linux 7 through 10 (kernel and kernel-rt), Red Hat In-Vehicle OS 2, and OpenShift Container Platform 4 and 5 are marked not affected because the vulnerable code is not present in the shipped kernels, and Red Hat Enterprise Linux 6 Extended Life-cycle Support is out of support scope.

The CVSS score(s) listed for this vulnerability do not reflect the associated product's status, and are included for informational purposes to better understand the severity of this vulnerability.

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.