CVE-2026-45885

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, <cbb9b07f88a9ef6518934c41eb3e8cf840d657d5, 0, 7.0, <3ff75cba1c98349a23a8f9333981deba1972cc11, 6.1.165, 6.12.75, <2ce2334be155bd8bad6377e99984246ce4dbd08c, <f3fbe309c9bfe1aac1e2b26543e9dc4829f3275a, <e261be6f18929f2397cd54cd583a2df624c129c1, 874b2adbed1253a11549cb9b7b912ab65fea9cf2, <=5.10.*, <=6.6.*, <2841bbb5a35c4449c0a0458e8e476b2a62f95147, <=6.19.*, 4.13, <642f33e34b969eedec334738fd5df95d2dc42742, <=6.18.*, 6.6.128, <4.13, 5.10.252, 6.19.4, <=*, <c549dd3de4b3f6e726d1b8386d40ccf7d3abdbe4, <=5.15.*, 5.15.202, 6.18.14

Description

In the Linux kernel, the following vulnerability has been resolved: power: supply: cpcap-battery: 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-45885 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.*, <=6.12.*, <cbb9b07f88a9ef6518934c41eb3e8cf840d657d5, 0, 7.0, <3ff75cba1c98349a23a8f9333981deba1972cc11, 6.1.165, 6.12.75, <2ce2334be155bd8bad6377e99984246ce4dbd08c, <f3fbe309c9bfe1aac1e2b26543e9dc4829f3275a, <e261be6f18929f2397cd54cd583a2df624c129c1, 874b2adbed1253a11549cb9b7b912ab65fea9cf2, <=5.10.*, <=6.6.*, <2841bbb5a35c4449c0a0458e8e476b2a62f95147, <=6.19.*, 4.13, <642f33e34b969eedec334738fd5df95d2dc42742, <=6.18.*, 6.6.128, <4.13, 5.10.252, 6.19.4, <=*, <c549dd3de4b3f6e726d1b8386d40ccf7d3abdbe4, <=5.15.*, 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