Answer in brief
CVE-2026-53217 records a High severity (CVSS 8.6) vulnerability in net: mvpp2: sync RX data at the hardware packet offset. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-53217 records a High severity (CVSS 8.6) vulnerability in net: mvpp2: sync RX data at the hardware packet offset. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.6. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e1921168bbd4810de4197446e52f652cd0dd9541 <60412bdd1b2576659eac23a23d2d9ff96228a643 || >=e1921168bbd4810de4197446e52f652cd0dd9541 <19f8bc139e9b149d1e5bf75ae761d1bb8dd3e7d8 || >=e1921168bbd4810de4197446e52f652cd0dd9541 <a3ad9b5767c89531fc7dae951b51b0933dcf7051 || >=e1921168bbd4810de4197446e52f652cd0dd9541 <bede0f481b9137d73d1cf64309cbe4b94818a5d6 || >=e1921168bbd4810de4197446e52f652cd0dd9541 <23548007b3c66d628fc7d6b80d1e23be04ea10d9 || >=e1921168bbd4810de4197446e52f652cd0dd9541 <a13199fa224e9f776f4005d5037df03aa9ea8f37 || >=e1921168bbd4810de4197446e52f652cd0dd9541 <e302206ad84a407a7e5f3f6fe767ff5efaace689 || >=e1921168bbd4810de4197446e52f652cd0dd9541 <180235600934bef6add3be637c296d6cf3272e67 | 60412bdd1b2576659eac23a23d2d9ff96228a643, 19f8bc139e9b149d1e5bf75ae761d1bb8dd3e7d8, a3ad9b5767c89531fc7dae951b51b0933dcf7051, bede0f481b9137d73d1cf64309cbe4b94818a5d6, 23548007b3c66d628fc7d6b80d1e23be04ea10d9, a13199fa224e9f776f4005d5037df03aa9ea8f37, e302206ad84a407a7e5f3f6fe767ff5efaace689, 180235600934bef6add3be637c296d6cf3272e67 |
| Linux/Linuxgeneric | 5.5 | Not reported |
Published upstream
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 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 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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 8.6. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e1921168bbd4810de4197446e52f652cd0dd9541 <60412bdd1b2576659eac23a23d2d9ff96228a643 || >=e1921168bbd4810de4197446e52f652cd0dd9541 <19f8bc139e9b149d1e5bf75ae761d1bb8dd3e7d8 || >=e1921168bbd4810de4197446e52f652cd0dd9541 <a3ad9b5767c89531fc7dae951b51b0933dcf7051 || >=e1921168bbd4810de4197446e52f652cd0dd9541 <bede0f481b9137d73d1cf64309cbe4b94818a5d6 || >=e1921168bbd4810de4197446e52f652cd0dd9541 <23548007b3c66d628fc7d6b80d1e23be04ea10d9 || >=e1921168bbd4810de4197446e52f652cd0dd9541 <a13199fa224e9f776f4005d5037df03aa9ea8f37 || >=e1921168bbd4810de4197446e52f652cd0dd9541 <e302206ad84a407a7e5f3f6fe767ff5efaace689 || >=e1921168bbd4810de4197446e52f652cd0dd9541 <180235600934bef6add3be637c296d6cf3272e67 | 60412bdd1b2576659eac23a23d2d9ff96228a643, 19f8bc139e9b149d1e5bf75ae761d1bb8dd3e7d8, a3ad9b5767c89531fc7dae951b51b0933dcf7051, bede0f481b9137d73d1cf64309cbe4b94818a5d6, 23548007b3c66d628fc7d6b80d1e23be04ea10d9, a13199fa224e9f776f4005d5037df03aa9ea8f37, e302206ad84a407a7e5f3f6fe767ff5efaace689, 180235600934bef6add3be637c296d6cf3272e67 |
| Linux/Linuxgeneric | 5.5 | Not reported |
Published upstream
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 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 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.
Quoted source text, attributed separately from HOL analysis.