CVE-2026-53217

HIGHPre-NVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.6Exploit: None knownExposed: 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(medium)
EG Risk
43(Track)
EG Risk 43/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
Severity86% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

June 25, 2026

Last Modified

August 5, 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.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
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—

Data Freshness Timeline

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

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 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-53217 actively exploited?
CVE-2026-53217 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 57.2% of all scored CVEs.
What is the CVSS score of CVE-2026-53217?
CVE-2026-53217 has a CVSS v4.0 base score of 8.6 (CNA self-assessment; NVD's own analysis pending).
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

See which npm, PyPI, Go, and Maven packages are affected by 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