CVE-2026-53217
net: mvpp2: sync RX data at the hardware packet offset
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.
INFO
Published Date :
June 25, 2026, 9:16 a.m.
Last Modified :
July 2, 2026, 8:52 p.m.
Remotely Exploit :
Yes !
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
Solution
- Update the Linux kernel to include the fix.
- Ensure DMA sync covers packet data and Marvell header.
- Use dma_sync_single_range_for_cpu with appropriate offset.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-53217.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-53217 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-53217
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-53217 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-53217 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Jul. 02, 2026
Action Type Old Value New Value Added CWE NVD-CWE-noinfo Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.176 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.143 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.210 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13 up to (excluding) 6.18.36 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.12.94 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.19 up to (excluding) 7.0.13 *cpe:2.3:o:linux:linux_kernel:7.1:rc5:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc6:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc7:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.5 up to (excluding) 5.10.259 Added Reference Type kernel.org: https://git.kernel.org/stable/c/180235600934bef6add3be637c296d6cf3272e67 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/19f8bc139e9b149d1e5bf75ae761d1bb8dd3e7d8 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/23548007b3c66d628fc7d6b80d1e23be04ea10d9 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/60412bdd1b2576659eac23a23d2d9ff96228a643 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/a13199fa224e9f776f4005d5037df03aa9ea8f37 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/a3ad9b5767c89531fc7dae951b51b0933dcf7051 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/bede0f481b9137d73d1cf64309cbe4b94818a5d6 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/e302206ad84a407a7e5f3f6fe767ff5efaace689 Types: Patch -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jun. 28, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jun. 25, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': 'e1921168bbd4810de4197446e52f652cd0dd9541', 'lessThan': '60412bdd1b2576659eac23a23d2d9ff96228a643', 'versionType': 'git'}, {'status': 'affected', 'version': 'e1921168bbd4810de4197446e52f652cd0dd9541', 'lessThan': '19f8bc139e9b149d1e5bf75ae761d1bb8dd3e7d8', 'versionType': 'git'}, {'status': 'affected', 'version': 'e1921168bbd4810de4197446e52f652cd0dd9541', 'lessThan': 'a3ad9b5767c89531fc7dae951b51b0933dcf7051', 'versionType': 'git'}, {'status': 'affected', 'version': 'e1921168bbd4810de4197446e52f652cd0dd9541', 'lessThan': 'bede0f481b9137d73d1cf64309cbe4b94818a5d6', 'versionType': 'git'}, {'status': 'affected', 'version': 'e1921168bbd4810de4197446e52f652cd0dd9541', 'lessThan': '23548007b3c66d628fc7d6b80d1e23be04ea10d9', 'versionType': 'git'}, {'status': 'affected', 'version': 'e1921168bbd4810de4197446e52f652cd0dd9541', 'lessThan': 'a13199fa224e9f776f4005d5037df03aa9ea8f37', 'versionType': 'git'}, {'status': 'affected', 'version': 'e1921168bbd4810de4197446e52f652cd0dd9541', 'lessThan': 'e302206ad84a407a7e5f3f6fe767ff5efaace689', 'versionType': 'git'}, {'status': 'affected', 'version': 'e1921168bbd4810de4197446e52f652cd0dd9541', 'lessThan': '180235600934bef6add3be637c296d6cf3272e67', 'versionType': 'git'}], 'programFiles': ['drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '5.5'}, {'status': 'unaffected', 'version': '0', 'lessThan': '5.5', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.10.259', 'versionType': 'semver', 'lessThanOrEqual': '5.10.*'}, {'status': 'unaffected', 'version': '5.15.210', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.176', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.143', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.94', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.36', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.13', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c'], 'defaultStatus': 'affected'}] Added 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. Added Reference https://git.kernel.org/stable/c/180235600934bef6add3be637c296d6cf3272e67 Added Reference https://git.kernel.org/stable/c/19f8bc139e9b149d1e5bf75ae761d1bb8dd3e7d8 Added Reference https://git.kernel.org/stable/c/23548007b3c66d628fc7d6b80d1e23be04ea10d9 Added Reference https://git.kernel.org/stable/c/60412bdd1b2576659eac23a23d2d9ff96228a643 Added Reference https://git.kernel.org/stable/c/a13199fa224e9f776f4005d5037df03aa9ea8f37 Added Reference https://git.kernel.org/stable/c/a3ad9b5767c89531fc7dae951b51b0933dcf7051 Added Reference https://git.kernel.org/stable/c/bede0f481b9137d73d1cf64309cbe4b94818a5d6 Added Reference https://git.kernel.org/stable/c/e302206ad84a407a7e5f3f6fe767ff5efaace689