CVE-2026-98524

Description

A flaw was found in the Linux kernel's Reliable Datagram Sockets (RDS) subsystem. When memory region mapping fails during InfiniBand operations, the kernel can retain a stale reference to memory buffers that have already been released. A local attacker could exploit this flaw to trigger a use-after-free condition, potentially leading to local privilege escalation or a denial of service through a system crash.

Statement

A use after free in the RDS IB Fastreg MR error path occurs because rds_ib_map_frmr can retain a caller owned scatterlist pointer when DMA mapping fails. The caller can then unpin the pages and free the scatterlist while the MR is returned to the pool with the stale pointer still present. A later MR teardown or pool flush can pass the dangling scatterlist to __rds_ib_teardown_mr, and KASAN confirms a slab use after free read in this path. For the CVSS the PR:L reflects that a local user or process must access the RDS RDMA interface and trigger MR registration and cleanup operations. AC:H reflects the additional requirement to reach the DMA mapping failure path and later reuse or tear down the affected pooled MR. The issue is not directly network reachable based on the demonstrated call path even though RDS is a network subsystem. Impact is at least a local denial of service via kernel crash and in the worst case may allow high confidentiality and integrity impact through use after free exploitation and local privilege escalation.

Mitigation

--- CME Mitigation Guidance (2026-10-20) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to disable or restrict the RDS protocol and prevent unprivileged local users from creating RDS sockets or invoking rds_setsockopt on InfiniBand-enabled Linux systems: upgrade to the fixed release, which store the scatterlist in the MR only after DMA mapping succeeds, and unmap and clear MR fields if registration fails, closing RDS setsockopt calls triggering InfiniBand memory region mapping failures. Until patched, this is only a concern on Linux systems with local unprivileged user access permitting the creation of RDS sockets and invocation of rds_setsockopt — Non-Linux operating systems are unaffected — so Blacklist the rds and rds_ib kernel modules or restrict local unprivileged user permissions to open RDS sockets and execute rds_setsockopt operations. As a compensating measure, Deploy runtime memory error detection like KASAN to detect slab use-after-free conditions when the dangling scatterlist pointer is dereferenced during memory region teardown, Enable SLAB freelist randomization and pointer integrity verification to hinder exploitation of kernel slab memory corruption, Enforce SELinux in enforcing mode to restrict socket operations and confine post-exploitation actions of compromised processes, Deploy eBPF runtime security monitoring with Falco to detect anomalous kernel-level behavior or privilege escalation attempts via RDS setsockopt calls, Enable SMEP and SMAP to prevent the kernel from executing userspace code or directly accessing userspace data during memory corruption exploitation, and Enable kernel Control Flow Integrity and shadow call stack validation on indirect call targets to prevent control-flow hijacking. These controls limit blast radius and contain exploitation, but they do not fix the underlying slab use-after-free defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-301 SELinux (Enforcing Mode) (medium)

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/A7.8
Attack VectorLocalN/ALocal
Attack ComplexityHighN/ALow
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityHighN/AHigh
Integrity ImpactHighN/AHigh
Availability ImpactHighN/AHigh

Vector

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

cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Confidentiality

Technical Impact: Read Memory

Read operations on freed memory can sometimes leak sensitive information instead of causing a crash

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Frequently Asked Questions

Want to get errata notifications? Sign up here.