CVE-2026-53217

HIGHPre-NVD 8.68.6—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.6Exploit: 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: sync RX data at the hardware packet offset

mvpp2 programs the RX queue packet offset, so hardware writes received data at dma_addr + MVPP2_SKB_HEADROOM. The current CPU sync starts at dma_addr and only covers rx_bytes + MVPP2_MH_SIZE bytes, which syncs the unused headroom and misses the same number of bytes at the packet tail.

On non-coherent DMA systems this can leave the CPU reading stale cache contents for the end of the received frame.

Use dma_sync_single_range_for_cpu() with MVPP2_SKB_HEADROOM as the range offset so the sync covers the Marvell header and packet data actually written by hardware.

CVSS v3
8.6
EG Score
8.6(high)
EPSS
32.1%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 2, 2026

Advisory Details (8)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

net: mvpp2: sync RX data at the hardware packet offset - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: mvpp2: sync RX data at the hardware packet offset - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: mvpp2: sync RX data at the hardware packet offset - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: mvpp2: sync RX data at the hardware packet offset - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: mvpp2: sync RX data at the hardware packet offset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/60412bdd1b2576659eac23a23d2d9ff96228a643
generic

net: mvpp2: sync RX data at the hardware packet offset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/23548007b3c66d628fc7d6b80d1e23be04ea10d9
generic

net: mvpp2: sync RX data at the hardware packet offset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/19f8bc139e9b149d1e5bf75ae761d1bb8dd3e7d8
generic

net: mvpp2: sync RX data at the hardware packet offset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/180235600934bef6add3be637c296d6cf3272e67

Vendor Advisories for CVE-2026-53217(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 46× in last 7d / 58× 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.

  1. 2026-07-06 18:38 UTCEG score recompute
  2. 2026-07-06 18:38 UTCVendor advisory
  3. 2026-07-06 18:38 UTCGHSA enrichment
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 06:13 UTCEG score recompute
  7. 2026-07-06 06:13 UTCVendor advisory
  8. 2026-07-06 06:13 UTCGHSA enrichment
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 17:37 UTCEG score recompute
  12. 2026-07-05 17:37 UTCVendor advisory
  13. 2026-07-05 17:37 UTCGHSA enrichment
  14. 2026-07-05 05:16 UTCEG score recompute
  15. 2026-07-05 05:16 UTCVendor advisory
  16. 2026-07-05 05:15 UTCGHSA enrichment
  17. 2026-07-05 02:31 UTCEPSS rescore
  18. 2026-07-05 02:30 UTCEPSS rescore
  19. 2026-07-04 16:50 UTCEG score recompute
  20. 2026-07-04 16:50 UTCVendor advisory
  21. 2026-07-04 16:50 UTCGHSA enrichment
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-04 04:08 UTCEG score recompute
  25. 2026-07-04 04:08 UTCVendor advisory
Show 33 more
  1. 2026-07-04 04:08 UTCGHSA enrichment
  2. 2026-07-03 15:22 UTCEG score recompute
  3. 2026-07-03 15:22 UTCVendor advisory
  4. 2026-07-03 15:22 UTCGHSA enrichment
  5. 2026-07-03 03:00 UTCEG score recompute
  6. 2026-07-03 03:00 UTCVendor advisory
  7. 2026-07-03 03:00 UTCGHSA enrichment
  8. 2026-07-02 14:38 UTCEG score recompute
  9. 2026-07-02 14:38 UTCVendor advisory
  10. 2026-07-02 14:38 UTCGHSA enrichment
  11. 2026-07-02 02:17 UTCEG score recompute
  12. 2026-07-02 02:17 UTCVendor advisory
  13. 2026-07-02 02:17 UTCGHSA enrichment
  14. 2026-07-01 15:07 UTCEPSS rescore
  15. 2026-07-01 13:55 UTCEG score recompute
  16. 2026-07-01 13:55 UTCVendor advisory
  17. 2026-07-01 13:55 UTCGHSA enrichment
  18. 2026-07-01 01:34 UTCEG score recompute▲ 8.60
  19. 2026-07-01 01:34 UTCVendor advisory
  20. 2026-07-01 01:34 UTCGHSA enrichment
  21. 2026-06-30 23:22 UTCEPSS rescore
  22. 2026-06-29 14:06 UTCEPSS rescore
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-28 14:07 UTCEPSS rescore
  25. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 8.6 · severity → HIGH
  26. 2026-06-28 05:51 UTCEG score recompute
  27. 2026-06-28 05:51 UTCGHSA enrichment
  28. 2026-06-28 04:56 UTCEPSS rescore
  29. 2026-06-28 04:56 UTCEPSS rescore
  30. 2026-06-27 03:08 UTCEPSS rescore
  31. 2026-06-25 13:49 UTCEPSS rescore
  32. 2026-06-25 10:07 UTCEG score recompute
  33. 2026-06-25 10:07 UTCGHSA enrichment

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-53217?
CVE-2026-53217 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: net: mvpp2: sync RX data at the hardware packet offset mvpp2 programs the RX queue packet offset, so hardware writes received data at dmaaddr + MVPP2SKB_HEADROOM. The current CPU sync starts at dmaaddr and only covers rxbytes +…
When was CVE-2026-53217 disclosed?
CVE-2026-53217 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-53217 actively exploited?
CVE-2026-53217 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 32.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53217?
CVE-2026-53217 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-53217?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53217, 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-53217

Explore →

Is Your Infrastructure Affected by CVE-2026-53217?

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

Start Free Scan →Browse All CVEs