CVE-2026-45946

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <c4af8a98bb52825a5331ae1d0604c0ea6956ba4b, <=6.12.*, 341db343768bc44f3512facc464021730d64071c, 5.13.4, 0, <551672981fe227122258a25a385a05f5c0746ad6, 7.0, 6.1.165, 6.12.75, <5.14, <=6.6.*, 5.14, <f50433f2603def08b21a4bf2fd238687fb5cbde9, <=6.19.*, <=6.18.*, 1c1f13a006ed0d71bb5664c8b7e3e77a28da3beb, 6.6.128, 6.19.4, <=*, <43cbb78ee047b9b12d096d40e3be265969d4c1f8, <=5.15.*, <847eeb6c0efcd76c7def73857cf798a4fcd8f79b, <46dbda27b028d78087667e8280966b99cec015ca, <709db4b476e254579d9c48ec34d397a41ca0c407, 5.15.202, 6.18.14

Description

In the Linux kernel, the following vulnerability has been resolved: power: supply: ab8500: Fix use-after-free in power_supply_changed() Using the `devm_` variant for requesting IRQ _before_ the `devm_` variant for allocating/registering the `power_supply` handle, means that the `power_supply` handle will be deallocated/unregistered _before_ the interrupt handler (since `devm_` naturally deallocates in reverse allocation order). This means that during removal, there is a race condition where an interrupt can fire just _after_ the `power_supply` handle has been freed, *but* just _before_ the corresponding unregistration of the IRQ handler has run. This will lead to the IRQ handler calling `power_supply_changed()` with a freed `power_supply` handle. Which usually crashes the system or otherwise silently corrupts the memory... Note that there is a similar situation which can also happen during `probe()`; the possibility of an interrupt firing _before_ registering the `power_supply` handle. This would then lead to the nasty situation of using the `power_supply` handle *uninitialized* in `power_supply_changed()`. Commit 1c1f13a006ed ("power: supply: ab8500: Move to componentized binding") introduced this issue during a refactorization. Fix this racy use-after-free by making sure the IRQ is requested _after_ the registration of the `power_supply` handle.

Gravité et risque d'exploitation

CVE-2026-45946 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.17 %, ce qui la place devant 6.0 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <c4af8a98bb52825a5331ae1d0604c0ea6956ba4b, <=6.12.*, 341db343768bc44f3512facc464021730d64071c, 5.13.4, 0, <551672981fe227122258a25a385a05f5c0746ad6, 7.0, 6.1.165, 6.12.75, <5.14, <=6.6.*, 5.14, <f50433f2603def08b21a4bf2fd238687fb5cbde9, <=6.19.*, <=6.18.*, 1c1f13a006ed0d71bb5664c8b7e3e77a28da3beb, 6.6.128, 6.19.4, <=*, <43cbb78ee047b9b12d096d40e3be265969d4c1f8, <=5.15.*, <847eeb6c0efcd76c7def73857cf798a4fcd8f79b, <46dbda27b028d78087667e8280966b99cec015ca, <709db4b476e254579d9c48ec34d397a41ca0c407, 5.15.202, 6.18.14) 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