Kernel warning via unset V3D DMA segment limit
Published May 8, 2026 · Updated May 8, 2026
Incorrect DMA segment-size handling in the Linux Kernel V3D driver allows local users to trigger a kernel warning through V3D rendering. The driver leaves max_seg_size unset, so the DMA layer applies a 64 KB default while V3D buffer creation maps much larger scatter-gather segments and debug_dma_map_sg emits a warning. Reachability requires the V3D driver with CONFIG_DMA_API_DEBUG enabled; the published description does not establish a hang, crash, data disclosure, or data modification.
Summary
What happened
Incorrect DMA segment-size handling in the Linux Kernel V3D driver allows local users to trigger a kernel warning through V3D rendering. The driver leaves max_seg_size unset, so the DMA layer applies a 64 KB default while V3D buffer creation maps much larger scatter-gather segments and debug_dma_map_sg emits a warning. Reachability requires the V3D driver with CONFIG_DMA_API_DEBUG enabled; the published description does not establish a hang, crash, data disclosure, or data modification.
The record
- CVE
- CVE-2026-43302
- Published
- May 8, 2026
- Updated
- May 8, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-131
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 8, 2026CVE publishedPublication date reported by the CVE source.
- May 8, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0290934d30abe7c88e18140fd5184c3f386b1e44
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <14d0d6c8b4504a60cfeea74775ab2e0164019e65
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <225023e3619b81af6d8d0e680503fc2d68633023
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2663ef70c6123b2232190f917275e5c3175f97d0
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9eb018828b1b30dfba689c060735c50fc5b9f704
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <cf510785f74e74c54de40a43a955b7f844857487
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <db15f469a88d3bbeeaa9f8c9f5e74d856ba5d7d2
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
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