cveboard RSS feed

CVE-2026-89465

CVE.org · Published

Historical CVEsJSONAI instructions

Record status
Published
Identifier year (not publication year)
2026
Source publication
Source updated
Imported by cveboard
Source snapshot
cve_2026-10-24_midnight_baseline ·

Plain text

CNA source text (English)

power: supply: rt9455: quiesce delayed work before teardown

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.

Scoped product and version facts

Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.

Exploitation unknown; this catalogue does not assess exploitation.

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
unaffected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
e86d69dd786e94046b8f5be7df1b9a8226a40b2aaffectedgit442c60c08ec23ac45da0a58877cab05e0a58f4eaUnavailableNone listed
e86d69dd786e94046b8f5be7df1b9a8226a40b2aaffectedgitdf67c7a2fff8414aa766b8cd5ffe11ec1ca27d02UnavailableNone listed
e86d69dd786e94046b8f5be7df1b9a8226a40b2aaffectedgit1b9978433c61a9b46e48832a1ebceee1cf5c9eb4UnavailableNone listed
e86d69dd786e94046b8f5be7df1b9a8226a40b2aaffectedgit7323e562f6961e4b7bce3225cde4ecbc78260debUnavailableNone listed
e86d69dd786e94046b8f5be7df1b9a8226a40b2aaffectedgit3e7a1ebc32fad5a558254a478efd401c17a24381UnavailableNone listed

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
affected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
4.2affectedUnavailableUnavailableUnavailableNone listed
0unaffectedsemver4.2UnavailableNone listed
6.6.157unaffectedsemverUnavailable6.6.*None listed
6.12.109unaffectedsemverUnavailable6.12.*None listed
6.18.50unaffectedsemverUnavailable6.18.*None listed
7.2.4unaffectedsemverUnavailable7.2.*None listed
7.3unaffectedoriginal_commit_for_fixUnavailable*None listed