CVE-2026-90012
CVE CVE-2026-90012EUVD EUVD-2026-80620Published 2026-09-16T10:33:19.000ZLast changed 2026-09-16T14:41:29.000ZCVSS 9.8
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux e289df82344fecc104ad8326b9ab6da612b9c899 <5def8b6aaad44603740786262b95b6f77df52a1c; 6.11; patch: 6.12.110; e289df82344fecc104ad8326b9ab6da612b9c899 <367cea239fc93094e5c16a72724800e0358f5c46; patch: 7.2.5; e289df82344fecc104ad8326b9ab6da612b9c899 <a38051fa2ddedbc8ec15292c55e276880ec5b9a4; patch: 6.18.51; patch: 7.3-rc1; e289df82344fecc104ad8326b9ab6da612b9c899 <cc8354213ad6bd5fb8cc05a3fa3701188d086626; patch: 0
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.