CVE-2026-53217: net: mvpp2: sync RX data at the hardware packet offset

Published Jun 25, 2026
·
Updated

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 dmaaddr + MVPP2SKBHEADROOM. The current CPU sync starts at dmaaddr and only covers rxbytes + MVPP2MHSIZE 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 dmasyncsinglerangeforcpu() with MVPP2SKBHEADROOM as the range offset so the sync covers the Marvell header and packet data actually written by hardware.

Affected Software

16 affected componentsFixes available
Linux Linux kernel (mvpp2)
Microsoft azl3 kernel 6.6.141.1-1<6.6.143.1-1
6.6.143.1-1
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
Linux Linux kernel=7.1-rc2
Linux Linux kernel=7.1-rc3
Linux Linux kernel=7.1-rc4
Linux Linux kernel=7.1-rc5
Linux Linux kernel=7.1-rc6
Linux Linux kernel=7.1-rc7

Event History

Jun 25, 2026
CVE Published
via MITRE·08:39 AM
Data Sourced
via MITRE·08:39 AM
DescriptionSeverity
Data Sourced
via NVD·09:16 AM
RemedyDescriptionSeverityAffected Software
Jun 27, 2026
Data Sourced
via Microsoft·08:16 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:16 AM
DescriptionSeverity

Frequently Asked Questions

1

What is the severity of CVE-2026-53217?

The severity of CVE-2026-53217 is rated as high with a score of 8.6.

2

How do I fix CVE-2026-53217?

To fix CVE-2026-53217, update the Linux kernel to the latest patched version addressing the vulnerability.

3

What systems are affected by CVE-2026-53217?

CVE-2026-53217 affects systems running the Linux kernel that includes mvpp2, as well as specific versions of the Microsoft azl3 kernel.

4

What is the impact of CVE-2026-53217?

The impact of CVE-2026-53217 includes potential data corruption or unexpected behavior in the RX data handling in affected systems.

5

When was CVE-2026-53217 published?

CVE-2026-53217 was published on June 25, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203