CVE-2026-45936

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <bad8b61eb5059acd88349680e47839342dc89e94, <=6.12.*, 0, <3.9, 7.0, <b2ce982e2e0c888dc55c888ad0e20ea04daf2e6b, 6.1.165, 6.12.75, <0b29ffe4090a3fc7a7649de20e1eb1e53adddac7, <=5.10.*, <=6.6.*, <=6.19.*, <4350505e82b4f972ddb788e1c712c557c38859d0, <=6.18.*, 84d7b768748943db2bb658b43931fdab04c224cc, <589d4fe56713c6344cd9f8939f9c7621c85f0966, 6.6.128, 5.10.252, <77ea437faa4c06362e3ecfd2d7264eaa7ac1e82c, 6.19.4, <=*, <=5.15.*, <8c89aade8335e26a6a7dcda18992d15f51943927, 5.15.202, 6.18.14, <33751e28842bf5aee5ef7b2b8d5e456a069095cb, 3.9

Description

In the Linux kernel, the following vulnerability has been resolved: power: supply: goldfish: 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()`. 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-45936 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.1 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <bad8b61eb5059acd88349680e47839342dc89e94, <=6.12.*, 0, <3.9, 7.0, <b2ce982e2e0c888dc55c888ad0e20ea04daf2e6b, 6.1.165, 6.12.75, <0b29ffe4090a3fc7a7649de20e1eb1e53adddac7, <=5.10.*, <=6.6.*, <=6.19.*, <4350505e82b4f972ddb788e1c712c557c38859d0, <=6.18.*, 84d7b768748943db2bb658b43931fdab04c224cc, <589d4fe56713c6344cd9f8939f9c7621c85f0966, 6.6.128, 5.10.252, <77ea437faa4c06362e3ecfd2d7264eaa7ac1e82c, 6.19.4, <=*, <=5.15.*, <8c89aade8335e26a6a7dcda18992d15f51943927, 5.15.202, 6.18.14, <33751e28842bf5aee5ef7b2b8d5e456a069095cb, 3.9) 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