VulnerabilityPublished 17 Sep 2026Updated 21 Oct 2026

CVE-2026-90433: Linux kernel · spi: oc-tiny: switch to managed controller allocation

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in ef5cc4a8c088d05549f71950a72b5deff5000fd7 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:07 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in ef5cc4a8c088d05549f71950a72b5deff5000fd7, d710f43ce30975d197f73c543bfe47b958d8ba17, 9265fa8190312b87637def1382d36fc16de3b8e8 +2

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ ce792580ea2ce6f7259b45124e9ccc4574c31606, < ef5cc4a8c088d05549f71950a72b5deff5000fd7	Fixed in ef5cc4a8c088d05549f71950a72b5deff5000fd7
LinuxLinux	Affected ≥ ce792580ea2ce6f7259b45124e9ccc4574c31606, < d710f43ce30975d197f73c543bfe47b958d8ba17	Fixed in d710f43ce30975d197f73c543bfe47b958d8ba17
LinuxLinux	Affected ≥ ce792580ea2ce6f7259b45124e9ccc4574c31606, < 9265fa8190312b87637def1382d36fc16de3b8e8	Fixed in 9265fa8190312b87637def1382d36fc16de3b8e8
LinuxLinux	Affected ≥ ce792580ea2ce6f7259b45124e9ccc4574c31606, < 0260c94453a08491640e61f8cf0c384edbe7bd11	Fixed in 0260c94453a08491640e61f8cf0c384edbe7bd11
LinuxLinux	Affected ≥ ce792580ea2ce6f7259b45124e9ccc4574c31606, < 1cd16c8d68f58e54abb8f331d05469237200631f	Fixed in 1cd16c8d68f58e54abb8f331d05469237200631f
LinuxLinux	Affected =2.6.39	Fixed in–

Description

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.

References

Community reviews

Loading reviews…