Local kernel compromise via stale SPI controller
Published Apr 3, 2026 · Updated Apr 3, 2026
Use-after-free in the SPI controller registration path in Linux Kernel allows local users to compromise kernel memory after failed setup. When per-CPU statistics allocation fails, spi_register_controller omits device_del(), leaving the controller registered while cleanup releases associated resources. Reachability requires local device-management access and the uncommon allocation failure; subsequent stale accesses can disclose or corrupt kernel memory or crash the system.
Summary
What happened
Use-after-free in the SPI controller registration path in Linux Kernel allows local users to compromise kernel memory after failed setup. When per-CPU statistics allocation fails, spi_register_controller omits device_del(), leaving the controller registered while cleanup releases associated resources. Reachability requires local device-management access and the uncommon allocation failure; subsequent stale accesses can disclose or corrupt kernel memory or crash the system.
The record
- CVE
- CVE-2026-31389
- Published
- Apr 3, 2026
- Updated
- Apr 3, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 3, 2026CVE publishedPublication date reported by the CVE source.
- Apr 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.0
- Affected versionversion=6598b91b5ac32bc756d7c3000a31f775d4ead1c4 <0e23f50086da7d0b183dfeac26021acfcdee086b
- Affected versionversion=6598b91b5ac32bc756d7c3000a31f775d4ead1c4 <23b51bad2eb8787aa74324cfccefb258515ae5ba
- Affected versionversion=6598b91b5ac32bc756d7c3000a31f775d4ead1c4 <6bbd385b30c7fb6c7ee0669e9ada91490938c051
- Affected versionversion=6598b91b5ac32bc756d7c3000a31f775d4ead1c4 <80f3e8cd2b4ad355b2ad2024cf423f6d183404f7
- Affected versionversion=6598b91b5ac32bc756d7c3000a31f775d4ead1c4 <8634e05b08ead636e926022f4a98416e13440df9
- Affected versionversion=6598b91b5ac32bc756d7c3000a31f775d4ead1c4 <afe27c1f43aa57530011f419be6ddf71306565d2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo