Skip to content
VulniPulse
Advisory severityHigh8.1Vendor: MediumRed Hat Linux

High [CVE-2026-53151] Fix the ACK parser to extract the SACK table for parsing

This high-severity Red Hat Linux advisory covers CVE-2026-53151 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 9, Red Hat package: kernel-rt.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-53151 Source published Source updated

VulniPulse record published Record updated

CVE-2026-53151
Affected products & platforms
Red Hat LinuxLinux Kernel
Open source advisory

Summary

In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix the ACK parser to extract the SACK table for parsing Fix modification of the received skbuff in rxrpc_input_soft_acks() and a potential incorrect access of the buffer in a fragmented UDP packet (the packet would probably have to be deliberately pre-generated as fragmented) when AF_RXRPC tries to extract the contents of the SACK table by copying out the contents of the SACK table into a buffer before attempting to parse AF_RXRPC assumes that it can just call skb_condense() and then validly access the SACK table from skb->data and that it will be a flat buffer - but skb_condense() can silently fail to do anything under some circumstances.

Note that whilst rxrpc_input_soft_acks() should be able to parse extended ACKs, the rest of AF_RXRPC doesn't currently support that. Further, there's then no need to call skb_condense() in rxrpc_input_ack(), so don't.

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.

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.

Is CVE-2026-53151 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2026-53151 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2026-53151?

The advisory VulniPulse tracks names no fixed release. Follow Red Hat's guidance for workarounds and updates.

Confirm against the vendor advisory before you patch.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.

Official advisory · high-confidence parse· fetched 15 days ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists. Confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 15 days ago·verify at source

Mitigation checklist

Recommended fix / 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).

Official advisory · high-confidence parse· fetched 15 days ago·verify at source

Get an email when Red Hat Linux Kernel publishes the next one.

See Red Hat Linux Kernel's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat Linux Kernel
All Red Hat Linux advisories

iPhone and Android apps · New on the App Store

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.