CVE-2026-89465

Description

In the Linux kernel, the following vulnerability has been resolved: power: supply: rt9455: quiesce delayed work before teardown The threaded IRQ handler can queue pwr_rdy_work, max_charging_time_work and batt_presence_work. pwr_rdy_work and batt_presence_work can also queue max_charging_time_work, while batt_presence_work can requeue itself. rt9455_remove() cancels max_charging_time_work before batt_presence_work. The latter can therefore queue max_charging_time_work after it has already been cancelled: rt9455_remove() workqueue cancel pwr_rdy_work cancel max_charging_time_work batt_presence_work queues max_charging_time_work cancel batt_presence_work return devres frees rt9455_info max_charging_time_work dereferences rt9455_info The IRQ also remains registered until devres cleanup and can queue more work after any of the cancellation calls. If rt9455_hw_init() fails after the IRQ has been requested, probe returns without cancelling work that may already have been queued. A pending callback can then access rt9455_info after it has been freed. Register rt9455_cancel_all_delayed_works() through devm_add_action_or_reset() right after devm_power_supply_register(). devres invokes the action in reverse registration order, after the managed IRQ has been freed and before rt9455_info is released, so the delayed works are drained in both rt9455_remove() and the probe error path. Cancel pwr_rdy_work and batt_presence_work before max_charging_time_work because both can queue the latter. This issue was found by an in-house static analysis tool.

Gravité et risque d'exploitation

CVE-2026-89465 obtient un score CVSS de 8.4/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.14 %, ce qui la place devant 3.1 % des CVE référencées.

Que faire ?

• Vérifiez si Linux (versions <df67c7a2fff8414aa766b8cd5ffe11ec1ca27d02, <=6.12.*, <4.2, 0, 7.2.4, <=6.6.*, 6.6.157, <442c60c08ec23ac45da0a58877cab05e0a58f4ea, e86d69dd786e94046b8f5be7df1b9a8226a40b2a, <=6.18.*, <3e7a1ebc32fad5a558254a478efd401c17a24381, <=7.2.*, 4.2, <=*, <1b9978433c61a9b46e48832a1ebceee1cf5c9eb4, <7323e562f6961e4b7bce3225cde4ecbc78260deb, 6.18.50, 6.12.109, 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

• https://git.kernel.org/stable/c/442c60c08ec23ac45da0a58877cab05e0a58f4ea
• https://git.kernel.org/stable/c/df67c7a2fff8414aa766b8cd5ffe11ec1ca27d02
• https://git.kernel.org/stable/c/1b9978433c61a9b46e48832a1ebceee1cf5c9eb4
• https://git.kernel.org/stable/c/7323e562f6961e4b7bce3225cde4ecbc78260deb
• https://git.kernel.org/stable/c/3e7a1ebc32fad5a558254a478efd401c17a24381