CVE-2026-53216

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: 1%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

net: mvpp2: limit XDP frame size to the RX buffer

mvpp2 has short and long BM pools, and short pool buffers can be smaller than PAGE_SIZE. The XDP path nevertheless initializes every xdp_buff with PAGE_SIZE as frame size.

XDP helpers use frame_sz to validate tail growth and to derive the hard end of the data area. Advertising PAGE_SIZE for short buffers can let bpf_xdp_adjust_tail() grow a packet past the real allocation, corrupting memory or later tripping skb tailroom checks.

Initialize the XDP buffer with bm_pool->frag_size so XDP tailroom matches the actual buffer backing the packet.

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%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
41%
KEV
Not listed

Published

June 25, 2026

Last Modified

August 5, 2026

Advisory Details (7)

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

net: mvpp2: limit XDP frame size to the RX buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f3c6aa078927e6fe8121c9c591ddee8716c5305a
generic

net: mvpp2: limit XDP frame size to the RX buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9545cc5ef18ca22d031f2f47c157192460652359
generic

net: mvpp2: limit XDP frame size to the RX buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/910617a4e67dbdd5fdb39d9dc6a51e491e1b2c3e
generic

net: mvpp2: limit XDP frame size to the RX buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/994bd2b58d2bd08aa97ec0836cc813cfcb00d749
generic

net: mvpp2: limit XDP frame size to the RX buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3b8b0c3631b19faee53f0d15a49924129b063eec
generic

net: mvpp2: limit XDP frame size to the RX buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ec8e1e5842bc0dbd4c272761f4db3651eecd0339
generic

net: mvpp2: limit XDP frame size to the RX buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a3ee9231ccec6ec3be2de89c56f897055fd9eab1

Vendor Advisories for CVE-2026-53216(1)

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

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-29.29) @ resolute2026-08-30ubuntu
ubuntulinux-tools-aws-edge (7.0.0-1010.10~24.04.1) @ noble2026-08-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-29.29~24.04.2) @ noble2026-08-30ubuntu
ubuntulinux-tools-gke-hwe-26.04 (7.0.0-1005.6) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1010.10) @ resolute2026-08-30ubuntu

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1—

All Vendor Advisories

(7)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-53216?
CVE-2026-53216 is a critical vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: net: mvpp2: limit XDP frame size to the RX buffer mvpp2 has short and long BM pools, and short pool buffers can be smaller than PAGESIZE. The XDP path nevertheless initializes every xdpbuff with PAGE_SIZE as frame size. XDP helpers…
When was CVE-2026-53216 disclosed?
CVE-2026-53216 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-53216 actively exploited?
CVE-2026-53216 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 58.6% of all scored CVEs.
What is the CVSS score of CVE-2026-53216?
CVE-2026-53216 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53216?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53216, 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-53216

Explore →

Is Your Infrastructure Affected by CVE-2026-53216?

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

Start Free Scan →Browse All CVEs