CVE-2026-90410

Unknown

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.

SeverityUnknown
CVSS—
Exploit probability—
ProductLinux
PublishedSep 17, 2026
First seenSep 17, 2026

How to fix

Update
  • Linux Linux2382f18daa4303923d66526db984e9a38074a312, 29e37f768f35592e26477f703649bd2e6f18d857, f9452eba71fbfcee55c0b8e030ee3615e9f75f65, 3b544072185c3d19ddec621ec9f6897ea2d10ee3, 1a7958ce58dc95b06615df00c120ece4eb9ccc86, ea408a05dc8f18b4a184b88d6e19d2fd1acc1527 or later

Affected products

ProductAffected versionsFixed in
Linux Linux5b3bb5963ff23a344062aba04937533a6f575761 ≤ v < 2382f18daa4303923d66526db984e9a38074a312, 5b3bb5963ff23a344062aba04937533a6f575761 ≤ v < 29e37f768f35592e26477f703649bd2e6f18d857, 5b3bb5963ff23a344062aba04937533a6f575761 ≤ v < f9452eba71fbfcee55c0b8e030ee3615e9f75f65, 5b3bb5963ff23a344062aba04937533a6f575761 ≤ v < 3b544072185c3d19ddec621ec9f6897ea2d10ee3, 5b3bb5963ff23a344062aba04937533a6f575761 ≤ v < 1a7958ce58dc95b06615df00c120ece4eb9ccc86, 5b3bb5963ff23a344062aba04937533a6f575761 ≤ v < ea408a05dc8f18b4a184b88d6e19d2fd1acc1527, 3.142382f18daa4303923d66526db984e9a38074a312, 29e37f768f35592e26477f703649bd2e6f18d857, f9452eba71fbfcee55c0b8e030ee3615e9f75f65, 3b544072185c3d19ddec621ec9f6897ea2d10ee3, 1a7958ce58dc95b06615df00c120ece4eb9ccc86, ea408a05dc8f18b4a184b88d6e19d2fd1acc1527

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.