CVE-2026-53151

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-25. the CNA's CVSS baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

June 25, 2026

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated Sep 9, 2026
No patch confirmed yet.
generic

rxrpc: Fix the ACK parser to extract the SACK table for parsing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/333b6d5bb9f87827ac2639c737bf9613dbae7253
generic

rxrpc: Fix the ACK parser to extract the SACK table for parsing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/224298450be5c04d2a6ea1c2a94669d7ebf65d00
generic

rxrpc: Fix the ACK parser to extract the SACK table for parsing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/566c4c1244de50fbff1f89ff93c9d7b0fc256db4
generic

rxrpc: Fix the ACK parser to extract the SACK table for parsing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/775c5e89272a2615b72bb84f611ba66fa3b7493e
generic

rxrpc: Fix the ACK parser to extract the SACK table for parsing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5d1ae4e17a3ecd8561cdb4f4f70152f41039c4e1

Vendor Advisories for CVE-2026-53151(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(13)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)6.12.95-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1

Additional Vendor Advisories

(13)

Data Freshness Timeline

(refreshed 5× in last 7d / 164× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 584 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-02 14:12 UTCEPSS rescore
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 04:40 UTCEPSS rescore
  10. 2026-08-30 23:31 UTCVendor advisory
  11. 2026-08-30 23:30 UTCGHSA enrichment
  12. 2026-08-30 19:41 UTCEG score recompute
  13. 2026-08-30 19:41 UTCVendor advisory
  14. 2026-08-30 19:41 UTCGHSA enrichment
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-28 02:56 UTCEG score recompute
  19. 2026-08-28 02:56 UTCVendor advisory
  20. 2026-08-28 02:55 UTCGHSA enrichment
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-26 14:46 UTCEPSS rescore
  23. 2026-08-25 13:49 UTCEPSS rescore
  24. 2026-08-25 05:19 UTCVendor advisory
  25. 2026-08-25 05:18 UTCGHSA enrichment
Show 75 more
  1. 2026-08-25 01:36 UTCVendor advisory
  2. 2026-08-25 01:35 UTCGHSA enrichment
  3. 2026-08-24 21:52 UTCEG score recompute
  4. 2026-08-24 21:52 UTCVendor advisory
  5. 2026-08-24 21:52 UTCGHSA enrichment
  6. 2026-08-24 13:16 UTCEG score recompute
  7. 2026-08-24 13:16 UTCVendor advisory
  8. 2026-08-24 13:16 UTCGHSA enrichment
  9. 2026-08-24 04:31 UTCVendor advisory
  10. 2026-08-24 04:31 UTCGHSA enrichment
  11. 2026-08-23 23:11 UTCVendor advisory
  12. 2026-08-23 23:11 UTCGHSA enrichment
  13. 2026-08-23 18:56 UTCVendor advisory
  14. 2026-08-23 18:56 UTCGHSA enrichment
  15. 2026-08-23 15:12 UTCVendor advisory
  16. 2026-08-23 15:12 UTCGHSA enrichment
  17. 2026-08-23 11:29 UTCVendor advisory
  18. 2026-08-23 11:29 UTCGHSA enrichment
  19. 2026-08-23 07:46 UTCVendor advisory
  20. 2026-08-23 07:46 UTCGHSA enrichment
  21. 2026-08-23 02:27 UTCEG score recompute
  22. 2026-08-23 02:27 UTCVendor advisory
  23. 2026-08-23 02:26 UTCGHSA enrichment
  24. 2026-08-23 00:19 UTCEPSS rescore
  25. 2026-08-22 22:31 UTCVendor advisory
  26. 2026-08-22 22:31 UTCGHSA enrichment
  27. 2026-08-22 14:51 UTCVendor advisory
  28. 2026-08-22 14:51 UTCGHSA enrichment
  29. 2026-08-22 10:50 UTCVendor advisory
  30. 2026-08-22 10:50 UTCGHSA enrichment
  31. 2026-08-22 00:52 UTCEG score recompute
  32. 2026-08-22 00:52 UTCVendor advisory
  33. 2026-08-22 00:52 UTCGHSA enrichment
  34. 2026-08-21 23:49 UTCEPSS rescore
  35. 2026-08-21 21:09 UTCVendor advisory
  36. 2026-08-21 21:09 UTCGHSA enrichment
  37. 2026-08-21 17:27 UTCVendor advisory
  38. 2026-08-21 17:26 UTCGHSA enrichment
  39. 2026-08-21 12:54 UTCVendor advisory
  40. 2026-08-21 12:54 UTCGHSA enrichment
  41. 2026-08-21 09:11 UTCVendor advisory
  42. 2026-08-21 09:11 UTCGHSA enrichment
  43. 2026-08-21 05:10 UTCVendor advisory
  44. 2026-08-21 05:10 UTCGHSA enrichment
  45. 2026-08-20 23:33 UTCEG score recompute
  46. 2026-08-20 23:33 UTCVendor advisory
  47. 2026-08-20 23:32 UTCGHSA enrichment
  48. 2026-08-20 22:55 UTCEPSS rescore
  49. 2026-08-20 19:49 UTCVendor advisory
  50. 2026-08-20 19:49 UTCGHSA enrichment
  51. 2026-08-20 16:06 UTCVendor advisory
  52. 2026-08-20 16:06 UTCGHSA enrichment
  53. 2026-08-20 10:53 UTCVendor advisory
  54. 2026-08-20 10:53 UTCGHSA enrichment
  55. 2026-08-20 07:11 UTCEG score recompute
  56. 2026-08-20 07:11 UTCVendor advisory
  57. 2026-08-20 07:11 UTCGHSA enrichment
  58. 2026-08-19 17:04 UTCEPSS rescore
  59. 2026-08-19 14:14 UTCVendor advisory
  60. 2026-08-19 14:14 UTCGHSA enrichment
  61. 2026-08-19 10:31 UTCVendor advisory
  62. 2026-08-19 10:30 UTCGHSA enrichment
  63. 2026-08-19 05:42 UTCVendor advisory
  64. 2026-08-19 05:42 UTCGHSA enrichment
  65. 2026-08-19 01:34 UTCEG score recompute
  66. 2026-08-19 01:34 UTCVendor advisory
  67. 2026-08-19 01:34 UTCGHSA enrichment
  68. 2026-08-18 13:48 UTCEPSS rescore
  69. 2026-08-17 14:38 UTCEG score recompute
  70. 2026-08-17 14:38 UTCVendor advisory
  71. 2026-08-17 14:38 UTCGHSA enrichment
  72. 2026-08-17 13:47 UTCEPSS rescore
  73. 2026-08-17 10:55 UTCVendor advisory
  74. 2026-08-17 10:55 UTCGHSA enrichment
  75. 2026-08-17 07:12 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-53151?
CVE-2026-53151 is a critical vulnerability published on June 25, 2026. 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 rxrpcinputsoft_acks() and a potential incorrect access of the buffer in a fragmented UDP packet (the packet would probably…
When was CVE-2026-53151 disclosed?
CVE-2026-53151 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53151 actively exploited?
CVE-2026-53151 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 61.6% of all scored CVEs.
What is the CVSS score of CVE-2026-53151?
CVE-2026-53151 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53151?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53151, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53151

Explore →

Is Your Infrastructure Affected by CVE-2026-53151?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.