CVE-2026-45867

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <83c1bd466c514cb24ca6ef347c5aac76a13c4e1e, <=6.1.*, <f27eb76def5c07e4d7cc468b40741f19dafc83ce, <=6.12.*, 0, 7.0, 6.1.165, 6.12.75, <3291c51d4684d048dd2eb91b5b65fcfdaf72141f, <d023ef9f748b2090f7a9dbdd5c622b6ad99088ea, <=5.10.*, <=6.6.*, <=6.19.*, <697bb5dc0cb4791e244f3970b067bc1ef33be9d9, <4.9, <=6.18.*, 6.6.128, <0768e8525a46df103647ca5059b32320d7fd17e4, 5.10.252, <76a42ba547a9b2e2337894f67a4d9247445007d5, 6.19.4, <f2a0777b1e5a3cee1712c4d3e9095c0df8fc8cb3, <=*, 4.9, <=5.15.*, 5.15.202, a09209acd6a808794bdd7866af3678d1fd1d90e7, 6.18.14

Description

In the Linux kernel, the following vulnerability has been resolved: power: supply: act8945a: 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-45867 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 <83c1bd466c514cb24ca6ef347c5aac76a13c4e1e, <=6.1.*, <f27eb76def5c07e4d7cc468b40741f19dafc83ce, <=6.12.*, 0, 7.0, 6.1.165, 6.12.75, <3291c51d4684d048dd2eb91b5b65fcfdaf72141f, <d023ef9f748b2090f7a9dbdd5c622b6ad99088ea, <=5.10.*, <=6.6.*, <=6.19.*, <697bb5dc0cb4791e244f3970b067bc1ef33be9d9, <4.9, <=6.18.*, 6.6.128, <0768e8525a46df103647ca5059b32320d7fd17e4, 5.10.252, <76a42ba547a9b2e2337894f67a4d9247445007d5, 6.19.4, <f2a0777b1e5a3cee1712c4d3e9095c0df8fc8cb3, <=*, 4.9, <=5.15.*, 5.15.202, a09209acd6a808794bdd7866af3678d1fd1d90e7, 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