CVE-2026-43302
DMA API Debug Warning in Linux Kernel V3D Driver
Publication date: 2026-05-08
Last updated on: 2026-05-08
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 6.12.53 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's V3D rendering component when the CONFIG_DMA_API_DEBUG option is enabled. The issue arises because the 'max_seg_size' parameter, which defines the maximum DMA segment size, is not set. By default, the kernel assumes a maximum segment size of 64K, but the V3D device attempts to map a segment longer than this limit, causing debug warnings about segment size mismatches.
The problem is that the DMA mapping segment length exceeds what the device claims to support, leading to warnings during debug operations. The fix involves setting 'max_seg_size' to the maximum supported value to prevent these debug warnings.
How can this vulnerability impact me? :
This vulnerability primarily causes debug warnings related to DMA segment size mismatches when using V3D rendering with debug DMA API enabled. It does not indicate a security breach or direct functional failure but may lead to confusion or difficulty in debugging kernel operations involving DMA.
There is no indication from the provided information that this vulnerability leads to data corruption, privilege escalation, or denial of service. Its impact is limited to debug message noise and potential developer confusion.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring kernel debug warnings related to DMA segment size mismatches when using V3D rendering with CONFIG_DMA_API_DEBUG enabled.
Specifically, look for kernel log messages indicating a segment size mismatch such as warnings from debug_dma_map_sg about mapping scatter-gather segments longer than the device supports.
You can check the kernel logs for these warnings using commands like:
- dmesg | grep -i 'debug_dma_map_sg'
- journalctl -k | grep -i 'debug_dma_map_sg'
- grep -i 'mapping sg segment longer' /var/log/kern.log
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is resolved by setting the DMA segment size (max_seg_size) to the maximum supported value to avoid debug warnings and segment size mismatches.
Immediate mitigation steps include:
- Ensure that the Linux kernel is updated to a version where this issue is fixed.
- If possible, disable CONFIG_DMA_API_DEBUG to prevent debug warnings until the kernel is updated.
- Review and apply any patches or kernel updates provided by your distribution that address this issue.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information about CVE-2026-43302 does not include any details regarding its impact on compliance with common standards and regulations such as GDPR or HIPAA.