CVE 9.8 CRITICAL

rxrpc: Fix the ACK parser to extract the SACK table for parsing_CVE-2026-53151

9.8 / 10
CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Description

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.

AI Analysis

A vulnerability in the Linux kernel's rxrpc module allows for potential incorrect access of the buffer in a fragmented UDP packet, leading to a denial of service or code execution.

Basic Information

ID CVE-2026-53151
Source Linux
Published Jun 25, 2026 at 08:38
Modified Jun 28, 2026 at 06:39

Affected Product

Vendor Linux
Product Linux
Version d57a3a151660902091491ac2633134e1be92557f
Affected Versions Linux Linux d57a3a151660902091491ac2633134e1be92557f
Linux Linux d57a3a151660902091491ac2633134e1be92557f
Linux Linux d57a3a151660902091491ac2633134e1be92557f
Linux Linux 6.2

AI Assessment

AI Score 9.8 / 10
AI Severity Critical
Vendor Linux
Product Linux Kernel
Version 6.2, d57a3a151660902091491ac2633134e1be92557f

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.