Answer in brief
CVE-2026-90410 records a Unknown severity vulnerability in spi: davinci: switch to managed controller allocation. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5b3bb5963ff23a344062aba04937533a6f575761 <29e37f768f35592e26477f703649bd2e6f18d857 || >=5b3bb5963ff23a344062aba04937533a6f575761 <f9452eba71fbfcee55c0b8e030ee3615e9f75f65 || >=5b3bb5963ff23a344062aba04937533a6f575761 <3b544072185c3d19ddec621ec9f6897ea2d10ee3 || >=5b3bb5963ff23a344062aba04937533a6f575761 <1a7958ce58dc95b06615df00c120ece4eb9ccc86 || >=5b3bb5963ff23a344062aba04937533a6f575761 <ea408a05dc8f18b4a184b88d6e19d2fd1acc1527 | 29e37f768f35592e26477f703649bd2e6f18d857, f9452eba71fbfcee55c0b8e030ee3615e9f75f65, 3b544072185c3d19ddec621ec9f6897ea2d10ee3, 1a7958ce58dc95b06615df00c120ece4eb9ccc86, ea408a05dc8f18b4a184b88d6e19d2fd1acc1527 |
| Linux/Linuxgeneric | 3.14 | Not reported |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.