CVE-2026-31389
Use-After-Free in Linux Kernel SPI Controller Registration
Publication date: 2026-04-03
Last updated on: 2026-05-20
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | From 6.2 (inc) to 6.6.130 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.78 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.18.20 (exc) |
| linux | linux_kernel | From 6.19 (inc) to 6.19.10 (exc) |
| linux | linux_kernel | From 6.0 (inc) to 6.1.167 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?
The vulnerability has been resolved by fixing the use-after-free issue in the Linux kernel related to SPI controller registration failure.
To mitigate this vulnerability, you should update your Linux kernel to a version that includes this fix.
How can this vulnerability impact me? :
The use-after-free vulnerability can cause the system to access freed memory, which may lead to system instability, crashes, or potential execution of arbitrary code.
Such issues can compromise the reliability and security of the Linux kernel, potentially affecting any system using the vulnerable SPI controller registration code.
Can you explain this vulnerability to me?
This vulnerability is a use-after-free issue in the Linux kernel related to the SPI (Serial Peripheral Interface) controller registration process.
Specifically, if the allocation of per-CPU statistics fails during the controller registration, the driver does not properly deregister from the driver core. This leads to use-after-free of driver resources and unclocked register accesses.