In the Linux kernel, the following vulnerability has been resolved: spi: rockchip-sfc: Fix DMA-API usage Use DMA-API dma_map_single() call for… (CVE-2025-40356)
A vulnerability in the Linux kernel's rockchip-sfc SPI driver related to improper DMA-API usage has been resolved. The issue involved using an incorrect method (virt_to_phys()) to obtain the DMA address of the transfer buffer instead of the proper dma_map_single() call. This caused DMA-API debug warnings and potential synchronization issues. The fix replaces the incorrect usage with the correct DMA-API call.
AI Analysis
Technical Summary
The Linux kernel's rockchip-sfc SPI driver improperly used virt_to_phys() to obtain the DMA address of the transfer buffer, which is not the correct method for DMA operations. This misuse triggered DMA-API debug warnings indicating that the driver attempted to synchronize DMA memory it had not allocated. The vulnerability was addressed by replacing the incorrect address retrieval with the proper dma_map_single() DMA-API call, ensuring correct DMA memory handling and synchronization.
Potential Impact
The vulnerability could lead to incorrect DMA memory synchronization, potentially causing data corruption or system instability. The CVSS vector indicates local attack vector with low complexity, requiring low privileges but no user interaction, and impacts confidentiality, integrity, and availability at a high level. However, there are no known exploits in the wild.
Mitigation Recommendations
A fix is available that corrects the DMA-API usage in the rockchip-sfc SPI driver by using dma_map_single() instead of virt_to_phys(). Users should apply the official Linux kernel updates that include this patch to remediate the vulnerability. Patch status is not explicitly confirmed in the provided data; check the vendor or Linux kernel advisories for the specific fixed versions and update accordingly.
In the Linux kernel, the following vulnerability has been resolved: spi: rockchip-sfc: Fix DMA-API usage Use DMA-API dma_map_single() call for… (CVE-2025-40356)
Description
A vulnerability in the Linux kernel's rockchip-sfc SPI driver related to improper DMA-API usage has been resolved. The issue involved using an incorrect method (virt_to_phys()) to obtain the DMA address of the transfer buffer instead of the proper dma_map_single() call. This caused DMA-API debug warnings and potential synchronization issues. The fix replaces the incorrect usage with the correct DMA-API call.
CVSS v3.1
Score 7.8high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's rockchip-sfc SPI driver improperly used virt_to_phys() to obtain the DMA address of the transfer buffer, which is not the correct method for DMA operations. This misuse triggered DMA-API debug warnings indicating that the driver attempted to synchronize DMA memory it had not allocated. The vulnerability was addressed by replacing the incorrect address retrieval with the proper dma_map_single() DMA-API call, ensuring correct DMA memory handling and synchronization.
Potential Impact
The vulnerability could lead to incorrect DMA memory synchronization, potentially causing data corruption or system instability. The CVSS vector indicates local attack vector with low complexity, requiring low privileges but no user interaction, and impacts confidentiality, integrity, and availability at a high level. However, there are no known exploits in the wild.
Mitigation Recommendations
A fix is available that corrects the DMA-API usage in the rockchip-sfc SPI driver by using dma_map_single() instead of virt_to_phys(). Users should apply the official Linux kernel updates that include this patch to remediate the vulnerability. Patch status is not explicitly confirmed in the provided data; check the vendor or Linux kernel advisories for the specific fixed versions and update accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-99cm-3rm5-ghgx
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2025-40356"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a6b72d49c2644c7f8478f1e
Added to database: 07/30/2026, 15:50:44 UTC
Last enriched: 07/30/2026, 17:53:48 UTC
Last updated: 09/10/2026, 19:38:45 UTC
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.