CVE-2026-90410: Linux kernel · spi: davinci: switch to managed controller allocation
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f9452eba71fbfcee55c0b8e030ee3615e9f75f65 : patch Linux kernel soon.
Data as of 30 Oct 2026, 13:04 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in f9452eba71fbfcee55c0b8e030ee3615e9f75f65, ea408a05dc8f18b4a184b88d6e19d2fd1acc1527, 2382f18daa4303923d66526db984e9a38074a312 +3
Exploitation evidence
Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
This vulnerability has been fixed in the Linux kernel by switching to managed controller allocation with devm_spi_alloc_host() and adjusting the interrupt and clock resource release order. Users should update to a Linux kernel version that includes the fix identified by the commit hashes provided. No additional mitigation is required once the fix is applied.
Description
A use-after-free vulnerability in the Linux kernel's davinci SPI controller driver was addressed by switching to managed controller allocation. The issue arises because the controller is allocated non-managed while the interrupt is registered with a managed request, causing a late interrupt to access freed memory. The fix involves using devm_spi_alloc_host() to ensure proper release order and explicitly draining interrupts before disabling the controller.
References
- git.kernel.org/stable/c/2382f18daa4303923d66526db984e9a38074a312 (opens in a new tab)
- git.kernel.org/stable/c/29e37f768f35592e26477f703649bd2e6f18d857 (opens in a new tab)
- git.kernel.org/stable/c/f9452eba71fbfcee55c0b8e030ee3615e9f75f65 (opens in a new tab)
- git.kernel.org/stable/c/3b544072185c3d19ddec621ec9f6897ea2d10ee3 (opens in a new tab)
- git.kernel.org/stable/c/1a7958ce58dc95b06615df00c120ece4eb9ccc86 (opens in a new tab)
- git.kernel.org/stable/c/ea408a05dc8f18b4a184b88d6e19d2fd1acc1527 (opens in a new tab)