CVE-2026-90410

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.12.*, 0, 5b3bb5963ff23a344062aba04937533a6f575761, 6.18.52, <1a7958ce58dc95b06615df00c120ece4eb9ccc86, <=6.6.*, 6.6.157, <3b544072185c3d19ddec621ec9f6897ea2d10ee3, 7.2.6, <ea408a05dc8f18b4a184b88d6e19d2fd1acc1527, <=6.18.*, <=7.2.*, 6.12.110, 3.14, <3.14, <f9452eba71fbfcee55c0b8e030ee3615e9f75f65, <=*, <29e37f768f35592e26477f703649bd2e6f18d857, 7.3

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.

Gravité et risque d'exploitation

CVE-2026-90410 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.21 %, ce qui la place devant 10.4 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.12.*, 0, 5b3bb5963ff23a344062aba04937533a6f575761, 6.18.52, <1a7958ce58dc95b06615df00c120ece4eb9ccc86, <=6.6.*, 6.6.157, <3b544072185c3d19ddec621ec9f6897ea2d10ee3, 7.2.6, <ea408a05dc8f18b4a184b88d6e19d2fd1acc1527, <=6.18.*, <=7.2.*, 6.12.110, 3.14, <3.14, <f9452eba71fbfcee55c0b8e030ee3615e9f75f65, <=*, <29e37f768f35592e26477f703649bd2e6f18d857, 7.3) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références