CVE-2025-40356
BaseFortify
Publication date: 2025-12-16
Last updated on: 2025-12-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| rockchip | rockchip_sfc | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel's rockchip-sfc SPI driver involves incorrect usage of the DMA-API. The driver was using virt_to_phys() to get the physical address of the transfer buffer instead of the proper dma_map_single() call. This misuse caused a DMA-API debug warning because the driver tried to synchronize DMA memory it had not allocated correctly. The fix replaces the incorrect method with the correct dma_map_single() call to properly obtain the DMA address.
How can this vulnerability impact me? :
The impact of this vulnerability is primarily related to incorrect DMA memory synchronization, which can lead to system instability or unexpected behavior in the SPI driver. It may cause debug warnings and potentially affect data integrity during SPI memory operations, but no direct security impact such as privilege escalation or data leakage is indicated.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring the kernel logs for the specific DMA-API debug warning related to the rockchip-sfc driver. You can use the command 'dmesg | grep -i dma-api' or 'journalctl -k | grep -i dma-api' to look for messages like: 'DMA-API: rockchip-sfc fe300000.spi: device driver tries to sync DMA memory it has not allocated'. This indicates the presence of the issue.
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the Linux kernel to a version where the rockchip-sfc driver uses the correct DMA-API dma_map_single() call instead of virt_to_phys(). This fix resolves the DMA-API debug warning and prevents improper DMA memory synchronization. If updating the kernel is not immediately possible, monitoring for the debug warning and avoiding workloads that trigger the issue may reduce risk.