CVE-2026-90012

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.

• https://git.kernel.org/stable/c/367cea239fc93094e5c16a72724800e0358f5c46
• https://git.kernel.org/stable/c/5def8b6aaad44603740786262b95b6f77df52a1c
• https://git.kernel.org/stable/c/a38051fa2ddedbc8ec15292c55e276880ec5b9a4
• https://git.kernel.org/stable/c/cc8354213ad6bd5fb8cc05a3fa3701188d086626

Published

Sep 16, 2026

Last Modified

Sep 16, 2026

Status

Received

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-90006In the Linux kernel, the following vulnerability has been re…
• CVE-2026-90007In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-90008In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-90009In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-90010In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-90011In the Linux kernel, the following vulnerability has been re…9.1
• CVE-2026-90013In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-90014In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-90015In the Linux kernel, the following vulnerability has been re…
• CVE-2026-90016In the Linux kernel, the following vulnerability has been re…7.1
• CVE-2026-90017In the Linux kernel, the following vulnerability has been re…7.1
• CVE-2026-90018In the Linux kernel, the following vulnerability has been re…8.8