CVE-2026-53217net: mvpp2: sync RX data at the hardware packet offset
- 8.6HighCVSS base score
- 0.38%Exploitation in 30 daysEPSS · top 67% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 16 days later
· 16 days later
Published
- 4 months later
· 4 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L |
| NVDNVD · Modified | 3.1 | High8.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L |
- EPSS (exploitation in 30 days)
- 0.38% · top 67% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.6.
Affected products
- affected e1921168bbd4810de4197446e52f652cd0dd9541 – < 60412bdd1b2576659eac23a23d2d9ff96228a643
- affected e1921168bbd4810de4197446e52f652cd0dd9541 – < 19f8bc139e9b149d1e5bf75ae761d1bb8dd3e7d8
- affected e1921168bbd4810de4197446e52f652cd0dd9541 – < a3ad9b5767c89531fc7dae951b51b0933dcf7051
- affected e1921168bbd4810de4197446e52f652cd0dd9541 – < bede0f481b9137d73d1cf64309cbe4b94818a5d6
- affected e1921168bbd4810de4197446e52f652cd0dd9541 – < 23548007b3c66d628fc7d6b80d1e23be04ea10d9
- affected e1921168bbd4810de4197446e52f652cd0dd9541 – < a13199fa224e9f776f4005d5037df03aa9ea8f37
- affected e1921168bbd4810de4197446e52f652cd0dd9541 – < e302206ad84a407a7e5f3f6fe767ff5efaace689
- affected e1921168bbd4810de4197446e52f652cd0dd9541 – < 180235600934bef6add3be637c296d6cf3272e67
- affected 5.5
- unaffected < 5.5
- unaffected 5.10.259 – ≤ 5.10.*
- unaffected 5.15.210 – ≤ 5.15.*
- unaffected 6.1.176 – ≤ 6.1.*
- unaffected 6.6.143 – ≤ 6.6.*
- unaffected 6.12.94 – ≤ 6.12.*
- unaffected 6.18.36 – ≤ 6.18.*
- unaffected 7.0.13 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References8
- https://git.kernel.org/stable/c/60412bdd1b2576659eac23a23d2d9ff96228a643 (opens in a new tab)
- https://git.kernel.org/stable/c/19f8bc139e9b149d1e5bf75ae761d1bb8dd3e7d8 (opens in a new tab)
- https://git.kernel.org/stable/c/a3ad9b5767c89531fc7dae951b51b0933dcf7051 (opens in a new tab)
- https://git.kernel.org/stable/c/bede0f481b9137d73d1cf64309cbe4b94818a5d6 (opens in a new tab)
- https://git.kernel.org/stable/c/23548007b3c66d628fc7d6b80d1e23be04ea10d9 (opens in a new tab)
- https://git.kernel.org/stable/c/a13199fa224e9f776f4005d5037df03aa9ea8f37 (opens in a new tab)
- https://git.kernel.org/stable/c/e302206ad84a407a7e5f3f6fe767ff5efaace689 (opens in a new tab)
- https://git.kernel.org/stable/c/180235600934bef6add3be637c296d6cf3272e67 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-39308 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-53217)Record last updated .