What is CVE-2026-90012?

CVE-2026-90012 is a Critical severity Linux kernel vulnerability with a CVSS score of 9.8 out of 10, affecting Linux kernel versions from 6.11 onward and patched in 6.12.110, 6.18.51, 7.2.5 and others. CVE-2026-90012 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-90012?

CVE-2026-90012 has a CVSS score of 9.8 out of 10, rated Critical severity. The vector string is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Is there a patch available for CVE-2026-90012?

Yes, CVE-2026-90012 has been patched. Fixed versions include 6.12.110, 6.18.51, 7.2.5 and others. If you are running Linux kernel 6.11 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-90012 actively exploited?

CVE-2026-90012 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-90012

Critical

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.

Package Linux Kernel

Published 2026-09-16

Last modified 2026-09-16

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

9.8

out of 10

Critical

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Vector string

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected versions

Linux kernel versions 6.11 and later are affected. Fixed in 6.12.110, 6.18.51, 7.2.5, 7.3-rc1 and their respective stable series.

Affected from

≥ 6.11

Fixed in

✓ 6.12.110 6.12.x ✓ 6.18.51 6.18.x ✓ 7.2.5 7.2.x ✓ 7.3-rc1

References

4 total

Details

CVE ID CVE-2026-90012

Severity Critical

CVSS score 9.8 / 10

CVSS version 3.1

Published 2026-09-16

Modified 2026-09-16

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-90012?

CVE-2026-90012 is a Critical severity Linux kernel vulnerability with a CVSS score of 9.8 out of 10 . It affects Linux kernel versions from 6.11 onward and has been patched in 6.12.110, 6.18.51, 7.2.5 and others. CVE-2026-90012 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-90012?

CVE-2026-90012 has a CVSS score of 9.8 out of 10, rated Critical severity (CVSS 3.1). The vector string is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
Is there a patch available for CVE-2026-90012?

Yes. CVE-2026-90012 has been patched. Fixed versions include 6.12.110, 6.18.51, 7.2.5 and others. If you are running Linux kernel 6.11 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-90012 actively exploited?

No. CVE-2026-90012 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.