CVSS 3.1
9.8 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCritical (9.8) in linux linux. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExplain CVE-2026-90012 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-90012?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-90012?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-90012 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | 6.11 and later |
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.12 | 6.12.110 |
| Linux | 6.18 | 6.18.51 |
| Linux | 7.2 | 7.2.5 |
| Linux | later releases | 7.3 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | linux-6.12 | 6.12.111-1~deb12u1 | DEBIAN-CVE-2026-90012 |
| Debian | 13 | linux | 6.12.111-1 | DEBIAN-CVE-2026-90012 |
| Debian | 14 | linux | 7.2.6-1 | DEBIAN-CVE-2026-90012 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-90012 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-90012 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-90012 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 more | no fix listed | UBUNTU-CVE-2026-90012 |
| Ubuntu | 24.04:LTS | linux-aws-7.0 | 7.0.0-1017.18~24.04.1 | UBUNTU-CVE-2026-90012 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-azure-fde-7.0 | 7.0.0-1019.19~24.04.1 | UBUNTU-CVE-2026-90012 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-gcp-7.0 | 7.0.0-1017.19~24.04.1 | UBUNTU-CVE-2026-90012 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-hwe-7.0 | 7.0.0-42.42~24.04.1 | UBUNTU-CVE-2026-90012 USN-8959-1 |
| Ubuntu | 24.04:LTS | linux-oracle-7.0 | 7.0.0-1016.18~24.04.1 | UBUNTU-CVE-2026-90012 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-riscv, linux-oem-6.8, linux-aws-6.14 and 27 more | no fix listed | UBUNTU-CVE-2026-90012 |
| Ubuntu | 24.04:LTS | linux-riscv-7.0 | 7.0.0-42.42.1~24.04.1 | UBUNTU-CVE-2026-90012 |
| Ubuntu | 26.04:LTS | linux | 7.0.0-42.42 | UBUNTU-CVE-2026-90012 USN-8959-1 |
| 12 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| SUSE | Linux Enterprise High Availability Extension 16.0 | kernel-default | 6.12.0-160000.41.1 | SUSE-SU-2026:24651-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | kernel-64kb, kernel-docs, kernel-syms and 6 more | 6.12.0-160000.41.1 | SUSE-SU-2026:24662-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | kernel-default-base | 6.12.0-160000.41.1.160000.2.32 | SUSE-SU-2026:24662-1 |
| SUSE | Linux Enterprise Server for NVIDIA 16.1 | kernel-nvidia64kb, kernel-source-nvidia | 6.12.0-160100.7.1 | SUSE-SU-2026:24705-1 |
| SUSE | Linux Micro 6.2 | kernel-default-base | 6.12.0-160000.41.1.160000.2.32 | SUSE-SU-2026:24643-1 |
| SUSE | Linux Micro 6.2 | kernel-rt, kernel-64kb, kernel-source and 1 more | 6.12.0-160000.41.1 | SUSE-SU-2026:24643-1 |
| SUSE | Linux Micro Extras 6.2 | kernel-syms, kernel-obs-build | 6.12.0-160000.41.1 | SUSE-SU-2026:24648-1 |
| openSUSE | Leap 16.0 | kernel-default-base | 6.12.0-160000.41.1.160000.2.31 | openSUSE-SU-2026:22266-1 |
| openSUSE | Leap 16.0 | kernel-rt, dtb-aarch64, kernel-64kb and 9 more | 6.12.0-160000.41.1 | openSUSE-SU-2026:22266-1 |
| openSUSE | Leap 16.1 | kernel-default-base | 6.12.0-160100.9.1.160100.3.14 | openSUSE-SU-2026:22309-1 |
| openSUSE | Leap 16.1 | kernel-nvidia64kb, kernel-syms-nvidia, kernel-source-nvidia | 6.12.0-160100.7.1 | openSUSE-SU-2026:22307-1 |
| openSUSE | Leap 16.1 | kernel-rt, dtb-aarch64, kernel-64kb and 9 more | 6.12.0-160100.9.1 | openSUSE-SU-2026:22309-1 |
| openSUSE | Tumbleweed | kernel-source | 7.2.7-1.1 | openSUSE-SU-2026:11880-1 |
| Alpaquita | 25 | linux-lts | 6.12.111-r0 | BELL-CVE-2026-90012 |
| Alpaquita | stream | linux-lts | 6.18.53-r0 | BELL-CVE-2026-90012 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.
Red Hat rates this Moderate.
A DMA mapping ownership bug in the SPI core can occur when __spi_map_msg sees a partial mapping failure. If RX mapping fails after TX mapping succeeds, tx_sg_mapped can remain set even though TX was already unmapped. If TX mapping fails on a later transfer, mappings from earlier transfers can remain active and later spi_unmap_msg may use a NULL or stale DMA device or release the same mapping twice. This can trigger a kernel oops through a NULL device dereference and may create limited DMA resource ownership risk. For the CVSS the PR:L is used because reliable triggering normally requires local ability to submit SPI transfers or control a local service or device node that can reach the SPI controller. The issue is not network reachable. Impact is at least local denial of service via kernel crash, with conservative limited confidentiality or integrity impact in the paranoid score due to stale device and double unmap behavior.
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 6 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Not affected | |
| Red Hat Enterprise Linux 8 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 9 | kernel | Not affected | |
| Red Hat Enterprise Linux 9 | kernel-rt | Not affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-8 | Not affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-9 | Not affected | |
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-9 | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-90012.