CVE-2026-45885: Linux kernel · power: supply: cpcap-battery: Fix use-after-free in power_supply_changed()
Source GCVE Database
Not known to be exploited · CVSS 7.8 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
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.
References
- nvd.nist.gov/vuln/detail/CVE-2026-45885 (opens in a new tab)
- git.kernel.org/stable/c/2841bbb5a35c4449c0a0458e8e476b2a62f95147 (opens in a new tab)
- git.kernel.org/stable/c/2ce2334be155bd8bad6377e99984246ce4dbd08c (opens in a new tab)
- git.kernel.org/stable/c/3ff75cba1c98349a23a8f9333981deba1972cc11 (opens in a new tab)
- git.kernel.org/stable/c/642f33e34b969eedec334738fd5df95d2dc42742 (opens in a new tab)
- git.kernel.org/stable/c/c549dd3de4b3f6e726d1b8386d40ccf7d3abdbe4 (opens in a new tab)
- git.kernel.org/stable/c/cbb9b07f88a9ef6518934c41eb3e8cf840d657d5 (opens in a new tab)
- git.kernel.org/stable/c/e261be6f18929f2397cd54cd583a2df624c129c1 (opens in a new tab)
- git.kernel.org/stable/c/f3fbe309c9bfe1aac1e2b26543e9dc4829f3275a (opens in a new tab)