Data corruption via missing PCIe coherency declaration
Published May 2, 2025 · Updated Aug 5, 2026
Improper cache coherency handling in Linux 5.16 through 6.2.8 allows local users to cause data corruption during PCIe DMA. The Qualcomm SC7280 PCIe device-tree node omits the dma-coherent property, so the kernel applies software DMA coherency operations to devices that are already cache coherent. Reachability is limited to arm64 systems using the SC7280 PCIe controller and an affected device tree, where PCIe DMA can corrupt kernel-managed data.
Summary
What happened
Improper cache coherency handling in Linux 5.16 through 6.2.8 allows local users to cause data corruption during PCIe DMA. The Qualcomm SC7280 PCIe device-tree node omits the dma-coherent property, so the kernel applies software DMA coherency operations to devices that are already cache coherent. Reachability is limited to arm64 systems using the SC7280 PCIe controller and an affected device tree, where PCIe DMA can corrupt kernel-managed data.
The record
- CVE
- CVE-2023-53043
- Published
- May 2, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 2, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.16
- Affected versionversion=92e0ee9f83b3bc1d5644b1dc36eae730d1e8694d <267b899375bf38944d915c9654d6eb434edad0ce
- Affected versionversion=92e0ee9f83b3bc1d5644b1dc36eae730d1e8694d <8a63441e83724fee1ef3fd37b237d40d90780766
- Affected versionversion=92e0ee9f83b3bc1d5644b1dc36eae730d1e8694d <e43bba938e2c9104bb4f8bc417ac4d7bb29755e1
What conditions does exploitation require?
What is affected?
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