CVE-2026-53151

Description

A flaw was found in the Linux kernel's AF_RXRPC subsystem. This vulnerability involves incorrect handling of fragmented UDP packets when parsing the SACK (Selective Acknowledgment) table. An attacker could potentially craft a fragmented UDP packet to trigger an incorrect buffer access within the kernel, which may lead to system instability or other undefined behavior.

Statement

The vulnerability in the Linux kernel AF_RXRPC subsystem occurs when rxrpc_input_soft_acks() parses a SACK table directly from skb->data, assuming a contiguous buffer. However, fragmented UDP packets may use non-linear sk_buffs, and skb_condense() may fail to linearize them, potentially causing out-of-bounds memory access, incorrect ACK processing, or a kernel crash.

Exploitation requires an active AF_RXRPC connection, a valid ACK context, and a specially crafted fragmented UDP packet passing protocol validation. Simply enabling AF_RXRPC does not make a system remotely exploitable; a malicious RxRPC peer or an attacker capable of injecting suitable traffic is a more realistic scenario.

For the CVSS, PR:N reflects that no target privileges are inherently required, while AC:H accounts for fragmentation, connection-state requirements, and ACK validation.

The likely impact is remote denial of service through invalid kernel memory access. Additional confidentiality or integrity impact remains uncertain, with no demonstrated reliable information disclosure, controlled out-of-bounds write, or privilege escalation.

Given the restricted attack surface, complex triggering conditions, and unproven exploitation beyond denial of service, MODERATE severity is defensible.

Mitigation

To mitigate this vulnerability, prevent the `rxrpc` kernel module from loading:

1. Create a configuration file to disable autoloading:

sh
echo "install rxrpc /bin/true" > /etc/modprobe.d/disable-rxrpc.conf

2. If the module is already loaded, unload it or restart the system:

sh
modprobe -r rxrpc

Caveats: Modifying kernel module configurations, unloading active modules, or restarting the system may interrupt running services. Disabling this module prevents functionality reliant on the AF_RXRPC protocol, including the in-kernel AFS filesystem (kAFS).

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 Score8.1N/A9.8
Attack VectorNetworkN/ANetwork
Attack ComplexityHighN/ALow
Privileges RequiredNoneN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityHighN/AHigh
Integrity ImpactHighN/AHigh
Availability ImpactHighN/AHigh

Vector

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

cve.org: CVSS:3.1/AV:N/AC:L/PR:N/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.