Heimdall Security Logo

CVE-2026-89945

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, <3be8380fb14d602cd833e5852e6d83c1e7eb1ceb, 5.15.221, 5.10.270, 0, <07a86575edc308e66b6c8873ed4a93ef3a063e55, 6.1.188, <4.10, 6.18.51, <4fe8a91a9266f1321c2d31ce67940a4e8b93559e, <=5.10.*, <=6.6.*, 4.10, 7.2.5, 6.6.157, <96982734e765c13c3db02067e1d5784682085f5c, <=6.18.*, <5a4fe7a87841af23ba80bae31b80355b16926cf4, <f4bfd755c52dfa7584e6c9374206b71b8895c997, 6.12.110, <=7.2.*, <=*, <5b063739619990d5de0c94c85d6e5be14e7cbdfe, <=5.15.*, c1124c09e1035cabdbc17d4538ae6f922086fec9, <4105a4c0678b2808fc8046b60321b4f1cc7dae75, 7.3

Description

In the Linux kernel, the following vulnerability has been resolved: ASoC: cs35l34: drain threaded IRQ before runtime suspend cs35l34_runtime_suspend() currently switches the codec into regcache_cache_only(true), asserts reset low, and powers the device off without first quiescing the threaded IRQ registered by devm_request_threaded_irq(). That leaves a window where cs35l34_irq_thread() can still run after suspend has removed live hardware access. A running system can reach this during runtime PM while the driver still has critical fault IRQs unmasked. If the threaded handler runs in that window, it reads volatile INT_STATUS_1..4 after cache_only has been enabled, ignores the regmap_read() failures, and can still execute the PROT_RELEASE_CTL release sequence or the BST fault power-down writes. Use disable_irq() before entering cache_only/reset-low/power-off so any in-flight threaded handler is drained and no new IRQ thread can run while the device is suspended. Re-enable the IRQ only after runtime_resume() has restored live register access with regcache_sync(). Since probe only logs request_threaded_irq() failures and keeps going, track whether the IRQ was actually installed before disabling or re-enabling it.

Gravité et risque d'exploitation

CVE-2026-89945 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.6 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, <3be8380fb14d602cd833e5852e6d83c1e7eb1ceb, 5.15.221, 5.10.270, 0, <07a86575edc308e66b6c8873ed4a93ef3a063e55, 6.1.188, <4.10, 6.18.51, <4fe8a91a9266f1321c2d31ce67940a4e8b93559e, <=5.10.*, <=6.6.*, 4.10, 7.2.5, 6.6.157, <96982734e765c13c3db02067e1d5784682085f5c, <=6.18.*, <5a4fe7a87841af23ba80bae31b80355b16926cf4, <f4bfd755c52dfa7584e6c9374206b71b8895c997, 6.12.110, <=7.2.*, <=*, <5b063739619990d5de0c94c85d6e5be14e7cbdfe, <=5.15.*, c1124c09e1035cabdbc17d4538ae6f922086fec9, <4105a4c0678b2808fc8046b60321b4f1cc7dae75, 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

Rechercher une autre CVE