CVE-2026-53215

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-25. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

net: mvpp2: refill RX buffers before XDP or skb use

The RX error path returns the current descriptor buffer to the hardware BM pool. That is only valid while the driver still owns the buffer.

mvpp2_rx_refill() can fail after the current buffer has been handed to XDP or attached to an skb. In those cases mvpp2_run_xdp() may have recycled, redirected, or queued the page for XDP_TX, and an skb free also retires the data buffer. Returning such a buffer to BM lets hardware DMA into memory that is no longer owned by the RX ring.

Refill the BM pool before handing the current buffer to XDP or to the skb. If the allocation fails there, drop the packet and return the still-owned current buffer to BM, preserving the pool depth. Once the refill succeeds, later local drops retire/free the current buffer instead of returning it to BM.

CVSS v3
9.8
EG Score
9.8(high)
EPSS
41.8%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 2, 2026

Advisory Details (7)

Auto-updated Jul 3, 2026
No patch confirmed yet.
generic

net: mvpp2: refill RX buffers before XDP or skb use - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: mvpp2: refill RX buffers before XDP or skb use - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: mvpp2: refill RX buffers before XDP or skb use - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: mvpp2: refill RX buffers before XDP or skb use - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8a2126c5afe89f8ceeb60a3afb9f075b736194cd
generic

net: mvpp2: refill RX buffers before XDP or skb use - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5e8e2a9624df72fca7c736b2966b2cbf6c9c3ff6
generic

net: mvpp2: refill RX buffers before XDP or skb use - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/580f92f27cb8724bcc4be98ee89890eab524a2ae
generic

net: mvpp2: refill RX buffers before XDP or skb use - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/02e1b5c4d3b4c658b72c145427cded1bba613fc1

Vendor Advisories for CVE-2026-53215(2)

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

Data Freshness Timeline

(refreshed 118× in last 7d / 130× 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 130 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53215?
CVE-2026-53215 is a critical vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: net: mvpp2: refill RX buffers before XDP or skb use The RX error path returns the current descriptor buffer to the hardware BM pool. That is only valid while the driver still owns the buffer. mvpp2rxrefill() can fail after the…
When was CVE-2026-53215 disclosed?
CVE-2026-53215 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53215 actively exploited?
CVE-2026-53215 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 41.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53215?
CVE-2026-53215 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-53215?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53215, 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

Explore the affected products and dependency analysis for CVE-2026-53215

Explore →

Is Your Infrastructure Affected by CVE-2026-53215?

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