{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90012 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90012 is a critical vulnerability in Linux, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-90012 and fix it if it is affected.\n\nWhat it is: CVE-2026-90012 is a critical vulnerability in Linux, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-90012 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-90012/ (Markdown: https://insights.sbomify.com/CVE-2026-90012/index.md)","id":"CVE-2026-90012","markdown":"https://insights.sbomify.com/CVE-2026-90012/index.md","name":"CVE-2026-90012","record":{"aliases":["BELL-CVE-2026-90012","DEBIAN-CVE-2026-90012","GHSA-xm4q-v74w-px7x","UBUNTU-CVE-2026-90012"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel SPI driver","requires_auth":"none","summary":"A null pointer dereference in the Linux kernel SPI driver can cause a system crash when DMA mapping fails partially.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"spi: Fix DMA mapping ownership on partial map failure","id":"CVE-2026-90012","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"tracing: Take trace_array reference when opening options file","id":"CVE-2026-90013"},"packages":[],"prev":{"headline":"scsi: target: iscsi: Reserve a terminator byte for the login payload","id":"CVE-2026-90011"},"products":["Linux"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A null pointer dereference in the Linux kernel SPI driver can cause a system crash when DMA mapping fails partially.","url":"https://insights.sbomify.com/CVE-2026-90012/"}