Stale packet-tail reads via incorrect DMA offset
Published Jun 25, 2026 · Updated Jun 25, 2026
Improper DMA synchronization in the Linux Kernel mvpp2 driver allows remote attackers to trigger stale packet-tail reads via received frames. The receive path synchronizes from the DMA buffer base instead of MVPP2_SKB_HEADROOM, leaving an equal-length packet-tail region unsynchronized. On non-coherent DMA systems with mvpp2, the CPU consumes residual cache data as frame bytes; public sources do not describe a remote retrieval path.
Summary
What happened
Improper DMA synchronization in the Linux Kernel mvpp2 driver allows remote attackers to trigger stale packet-tail reads via received frames. The receive path synchronizes from the DMA buffer base instead of MVPP2_SKB_HEADROOM, leaving an equal-length packet-tail region unsynchronized. On non-coherent DMA systems with mvpp2, the CPU consumes residual cache data as frame bytes; public sources do not describe a remote retrieval path.
The record
- CVE
- CVE-2026-53217
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 25, 2026CVE publishedPublication date reported by the CVE source.
- Jun 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.5
- Affected versionversion=e1921168bbd4810de4197446e52f652cd0dd9541 <180235600934bef6add3be637c296d6cf3272e67
- Affected versionversion=e1921168bbd4810de4197446e52f652cd0dd9541 <19f8bc139e9b149d1e5bf75ae761d1bb8dd3e7d8
- Affected versionversion=e1921168bbd4810de4197446e52f652cd0dd9541 <23548007b3c66d628fc7d6b80d1e23be04ea10d9
- Affected versionversion=e1921168bbd4810de4197446e52f652cd0dd9541 <60412bdd1b2576659eac23a23d2d9ff96228a643
- Affected versionversion=e1921168bbd4810de4197446e52f652cd0dd9541 <a13199fa224e9f776f4005d5037df03aa9ea8f37
- Affected versionversion=e1921168bbd4810de4197446e52f652cd0dd9541 <a3ad9b5767c89531fc7dae951b51b0933dcf7051
- Affected versionversion=e1921168bbd4810de4197446e52f652cd0dd9541 <bede0f481b9137d73d1cf64309cbe4b94818a5d6
- Affected versionversion=e1921168bbd4810de4197446e52f652cd0dd9541 <e302206ad84a407a7e5f3f6fe767ff5efaace689
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo