{"id":"CVE-2026-90012","url":"https://www.cyber-defence.io/tools/cve/CVE-2026-90012","generatedAt":"2026-09-20T13:19:31.755Z","title":"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.","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nspi: Fix DMA mapping ownership on partial map failure\n\nIf RX mapping fails after TX mapping succeeds, __spi_map_msg() unmaps\nTX but leaves tx_sg_mapped set. If TX mapping fails on a later\ntransfer, mappings created for earlier transfers remain active.\n\nIn both cases, cur_{tx,rx}_dma_dev have not yet been updated because they\nare assigned only after every transfer has been mapped. The subsequent\nspi_unmap_msg() may therefore unmap the TX mapping again or release\nearlier mappings using a NULL or stale device. Using a NULL device can\ntrigger an oops. An empty SG table does not prevent the NULL dereference\nbecause dma_unmap_sg_attrs() accesses the device before checking the\nentry count.\n\nPublish both mapping devices before mapping starts and unwind all\nfailures through __spi_unmap_msg(). This clears the mapping flags and\nreleases each mapping once with the device that created it.\n\nPublishing the devices before the loop also refreshes them when no\ntransfer needs mapping. No mapping flag is set in that case, so current\nusers do not use the pointers as mapping owners.","published":"2026-09-16T11:17:14.000Z","lastModified":"2026-09-16T15:18:25.000Z","status":"Received","sourceIdentifier":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","cvss":{"version":"3.1","score":9.8,"severity":"CRITICAL","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"},"cwe":[],"affected":[],"epss":{"score":0.00626,"percentile":0.48608,"date":"2026-09-19","history":[]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"high","text":"High impact if exploited, but EPSS currently rates exploitation as unlikely (0.63%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit."},"changes":[],"references":[{"url":"https://git.kernel.org/stable/c/367cea239fc93094e5c16a72724800e0358f5c46","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/5def8b6aaad44603740786262b95b6f77df52a1c","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/a38051fa2ddedbc8ec15292c55e276880ec5b9a4","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/cc8354213ad6bd5fb8cc05a3fa3701188d086626","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-90012","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}