← Back to the live CVE advisory feed

CVE-2026-90012: Linux

Severity

9.8 (CRITICAL)

Vendor

LINUX

Affected versions

e289df82344fecc104ad8326b9ab6da612b9c899 through before cc8354213ad6bd5fb8cc05a3fa3701188d086626; e289df82344fecc104ad83

Patch status

Patched

Published

2026-09-16T11:17:13.890

Modified

2026-09-16T15:18:24.870

Why it matters

Critical vulnerability requiring immediate validation against your environment.

Recommended admin actions

• Prioritize validation immediately due to critical CVSS severity.
• Compare installed versions against the affected version range in the advisory.

Technical summary

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.

View the official NVD record for CVE-2026-90012

CVE data is sourced from NVD/CNA records and optional enrichment. Validate against the vendor advisory before taking production action.