CVE-2026-90410spi: davinci: switch to managed controller allocation
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: spi: davinci: switch to managed controller allocation The controller is allocated with the non-managed spi_alloc_host() while the interrupt is registered with devm_request_threaded_irq(). During removal, spi_bitbang_stop() only unregisters the controller; the subsequent spi_controller_put() then frees the controller together with its embedded davinci_spi devdata, which is the IRQ handler's dev_id. The devm_request_threaded_irq() release action (free_irq()), which drains the handler, does not run until after .remove() returns. A late or latched interrupt can therefore reach davinci_spi_irq() and dereference already-freed memory. Switch to devm_spi_alloc_host() so that the devres LIFO order releases the controller only after free_irq() has drained the handler, and drop the now-redundant spi_controller_put() from .remove(). The probe error path is simplified to direct returns. The clock is acquired with devm_clk_get_enabled(), which is registered after the IRQ and thus released before it by the devres LIFO order. Drain the interrupt explicitly with devm_free_irq() before disabling the controller so that a late interrupt cannot access the registers of a clock-gated controller. This issue was found by an in-house static analysis tool.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 43 days later
· 43 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 88% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 5b3bb5963ff23a344062aba04937533a6f575761 – < 2382f18daa4303923d66526db984e9a38074a312
- affected 5b3bb5963ff23a344062aba04937533a6f575761 – < 29e37f768f35592e26477f703649bd2e6f18d857
- affected 5b3bb5963ff23a344062aba04937533a6f575761 – < f9452eba71fbfcee55c0b8e030ee3615e9f75f65
- affected 5b3bb5963ff23a344062aba04937533a6f575761 – < 3b544072185c3d19ddec621ec9f6897ea2d10ee3
- affected 5b3bb5963ff23a344062aba04937533a6f575761 – < 1a7958ce58dc95b06615df00c120ece4eb9ccc86
- affected 5b3bb5963ff23a344062aba04937533a6f575761 – < ea408a05dc8f18b4a184b88d6e19d2fd1acc1527
- affected 3.14
- unaffected < 3.14
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.157 – ≤ 6.6.*
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.52 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/2382f18daa4303923d66526db984e9a38074a312 (opens in a new tab)
- https://git.kernel.org/stable/c/29e37f768f35592e26477f703649bd2e6f18d857 (opens in a new tab)
- https://git.kernel.org/stable/c/f9452eba71fbfcee55c0b8e030ee3615e9f75f65 (opens in a new tab)
- https://git.kernel.org/stable/c/3b544072185c3d19ddec621ec9f6897ea2d10ee3 (opens in a new tab)
- https://git.kernel.org/stable/c/1a7958ce58dc95b06615df00c120ece4eb9ccc86 (opens in a new tab)
- https://git.kernel.org/stable/c/ea408a05dc8f18b4a184b88d6e19d2fd1acc1527 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-82071 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-90410)Record last updated .