CVE-2026-97954

Description

A flaw was found in the Linux kernel's Reliable Datagram Sockets (RDS) subsystem. This vulnerability allows a network user to cause a Denial of Service (DoS) by corrupting TCP communication streams. On systems configured with memory page sizes larger than 8 KB, the kernel incorrectly calculates buffer lengths when mapping memory pages for RDS congestion maps. Consequently, extraneous bytes are transmitted across the network connection and misread as message headers, corrupting the stream and causing connections to hang.

Statement

A moderate impact flaw was found in the Linux kernel's Reliable Datagram Sockets (RDS) subsystem. In rds_message_map_pages(), a full PAGE_SIZE length is assigned to every scatterlist entry even when the mapped total length ends in a partial page. Because the RDS congestion map is defined as 8192 bytes, on systems configured with a memory page size larger than 8 KB (for example 16 KB or 64 KB pages), the scatterlist maps bytes beyond the end of the congestion map. RDS-TCP transmits those extra bytes according to the scatterlist lengths, and the receiving peer interprets them as subsequent RDS message headers, corrupting the TCP stream and causing RDS-TCP connections to hang, which results in a denial of service against the RDS transport. Systems using a 4 KB page size are not affected, and triggering the flaw requires RDS-TCP on a system built with a larger page size, an uncommon configuration; for this reason Red Hat assesses the impact of this flaw as moderate. All currently listed Red Hat products, including Red Hat Enterprise Linux, Red Hat Enterprise Linux for Real Time, Red Hat In-Vehicle OS, and OpenShift Container Platform RHCOS components, are not affected because the vulnerable code is not present; Red Hat Enterprise Linux 6 Extended Lifecycle Support is out of support scope.

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.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score7N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityHighN/AN/A
Integrity ImpactHighN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.

Confidentiality

Technical Impact: Bypass Protection Mechanism

Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.

Other

Technical Impact: Varies by Context

The read operation could produce other undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.