CVE-2026-90433
CVE CVE-2026-90433EUVD EUVD-2026-82094Published 2026-09-17T16:09:53.000Z
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 6.12.110; ce792580ea2ce6f7259b45124e9ccc4574c31606 <0260c94453a08491640e61f8cf0c384edbe7bd11; ce792580ea2ce6f7259b45124e9ccc4574c31606 <ef5cc4a8c088d05549f71950a72b5deff5000fd7; ce792580ea2ce6f7259b45124e9ccc4574c31606 <d710f43ce30975d197f73c543bfe47b958d8ba17; patch: 7.3-rc1; ce792580ea2ce6f7259b45124e9ccc4574c31606 <1cd16c8d68f58e54abb8f331d05469237200631f; patch: 0; 2.6.39; patch: 7.2.6; patch: 6.18.52
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.