CVE-2026-53217
Last modified
CVE-2026-53217 is a high-severity vulnerability rated 8.6/10 on the CVSS scale. 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.. EPSS estimates a 0.40% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.5, < 5.10.259 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.210 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.176 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.143 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.94 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.36 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.13 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53217?
How severe is CVE-2026-53217?
How do I fix CVE-2026-53217?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-53211In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53212In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53213In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53214In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53215In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-53216In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-53218In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53219In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-5322A vulnerability has been found in AlejandroArciniegas mcp-da…7.3
- CVE-2026-53220In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53221In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-53222In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-53217?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
