Answer in brief
CVE-2026-90012 records a Unknown severity vulnerability in spi: Fix DMA mapping ownership on partial map failure. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e289df82344fecc104ad8326b9ab6da612b9c899 <cc8354213ad6bd5fb8cc05a3fa3701188d086626 || >=e289df82344fecc104ad8326b9ab6da612b9c899 <a38051fa2ddedbc8ec15292c55e276880ec5b9a4 || >=e289df82344fecc104ad8326b9ab6da612b9c899 <5def8b6aaad44603740786262b95b6f77df52a1c || >=e289df82344fecc104ad8326b9ab6da612b9c899 <367cea239fc93094e5c16a72724800e0358f5c46 | cc8354213ad6bd5fb8cc05a3fa3701188d086626, a38051fa2ddedbc8ec15292c55e276880ec5b9a4, 5def8b6aaad44603740786262b95b6f77df52a1c, 367cea239fc93094e5c16a72724800e0358f5c46 |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 16, 2026
In the Linux kernel, the following vulnerability has been resolved: spi: Fix DMA mapping ownership on partial map failure If RX mapping fails after TX mapping succeeds, __spi_map_msg() unmaps TX but leaves tx_sg_mapped set. If TX mapping fails on a later transfer, mappings created for earlier transfers remain active. In both cases, cur_{tx,rx}_dma_dev have not yet been updated because they are assigned only after every transfer has been mapped. The subsequent spi_unmap_msg() may therefore unmap the TX mapping again or release earlier mappings using a NULL or stale device. Using a NULL device can trigger an oops. An empty SG table does not prevent the NULL dereference because dma_unmap_sg_attrs() accesses the device before checking the entry count. Publish both mapping devices before mapping starts and unwind all failures through __spi_unmap_msg(). This clears the mapping flags and releases each mapping once with the device that created it. Publishing the devices before the loop also refreshes them when no transfer needs mapping. No mapping flag is set in that case, so current users do not use the pointers as mapping owners.
Quoted source text, attributed separately from HOL analysis.