Skip to main content
VulnerabilityPublished Updated

CVE-2026-53151: Linux kernel · Out-of-bounds Read

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in 224298450be5c04d2a6ea1c2a94669d7ebf65d00 : patch Linux kernel as a priority.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in 224298450be5c04d2a6ea1c2a94669d7ebf65d00, 775c5e89272a2615b72bb84f611ba66fa3b7493e, 566c4c1244de50fbff1f89ff93c9d7b0fc256db4 +2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ d57a3a151660902091491ac2633134e1be92557f, < 224298450be5c04d2a6ea1c2a94669d7ebf65d00
Fixed in
  • 224298450be5c04d2a6ea1c2a94669d7ebf65d00
LinuxLinuxAffected
  • ≥ d57a3a151660902091491ac2633134e1be92557f, < 775c5e89272a2615b72bb84f611ba66fa3b7493e
Fixed in
  • 775c5e89272a2615b72bb84f611ba66fa3b7493e
LinuxLinuxAffected
  • ≥ d57a3a151660902091491ac2633134e1be92557f, < 566c4c1244de50fbff1f89ff93c9d7b0fc256db4
Fixed in
  • 566c4c1244de50fbff1f89ff93c9d7b0fc256db4
LinuxLinuxAffected
  • ≥ d57a3a151660902091491ac2633134e1be92557f, < 333b6d5bb9f87827ac2639c737bf9613dbae7253
Fixed in
  • 333b6d5bb9f87827ac2639c737bf9613dbae7253
LinuxLinuxAffected
  • ≥ d57a3a151660902091491ac2633134e1be92557f, < 5d1ae4e17a3ecd8561cdb4f4f70152f41039c4e1
Fixed in
  • 5d1ae4e17a3ecd8561cdb4f4f70152f41039c4e1
LinuxLinuxAffected
  • =6.2
Fixed in–

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.

References

Community reviews

Loading reviews…