Answer in brief
CVE-2026-90433 records a Unknown severity vulnerability in spi: oc-tiny: 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 | >=ce792580ea2ce6f7259b45124e9ccc4574c31606 <0260c94453a08491640e61f8cf0c384edbe7bd11 || >=ce792580ea2ce6f7259b45124e9ccc4574c31606 <ef5cc4a8c088d05549f71950a72b5deff5000fd7 || >=ce792580ea2ce6f7259b45124e9ccc4574c31606 <1cd16c8d68f58e54abb8f331d05469237200631f || >=ce792580ea2ce6f7259b45124e9ccc4574c31606 <d710f43ce30975d197f73c543bfe47b958d8ba17 | 0260c94453a08491640e61f8cf0c384edbe7bd11, ef5cc4a8c088d05549f71950a72b5deff5000fd7, 1cd16c8d68f58e54abb8f331d05469237200631f, d710f43ce30975d197f73c543bfe47b958d8ba17 |
| Linux/Linuxgeneric | 2.6.39 | 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: oc-tiny: switch to managed controller allocation The controller is allocated with the non-managed spi_alloc_host() while the interrupt is registered with devm_request_irq(). During removal, spi_bitbang_stop() only unregisters the controller; the subsequent spi_controller_put() then frees the controller together with its embedded driver-private devdata, which is the IRQ handler's dev_id. The devm_request_irq() release action (free_irq()), which drains the handler, does not run until after .remove() returns. A late or latched interrupt can therefore reach tiny_spi_irq() and dereference already-freed memory (e.g. hw->base). 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. This issue was found by an in-house static analysis tool.
Quoted source text, attributed separately from HOL analysis.