High 7.8Published May 27, 2026

CVE-2026-45885power: supply: cpcap-battery: Fix use-after-free in power_supply_changed()

Updated under an hour ago (Oct 28, 2026, 2:20 AM ET)

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

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.

CVSS: 7.8 HIGH (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE): Not given
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Analyzed
Record last updated: May 27, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	from 874b2adbed1253a11549cb9b7b912ab65fea9cf2 before c549dd3de4b3f6e726d1b8386d40ccf7d3abdbe4; 874b2adbed1253a11549cb9b7b912ab65fea9cf2 builds before 3ff75cba1c98349a23a8f9333981deba1972cc11; 874b2adbed1253a11549cb9b7b912ab65fea9cf2 builds before 2ce2334be155bd8bad6377e99984246ce4dbd08c; from 874b2adbed1253a11549cb9b7b912ab65fea9cf2 before cbb9b07f88a9ef6518934c41eb3e8cf840d657d5; from 874b2adbed1253a11549cb9b7b912ab65fea9cf2 before f3fbe309c9bfe1aac1e2b26543e9dc4829f3275a; from 874b2adbed1253a11549cb9b7b912ab65fea9cf2 before 2841bbb5a35c4449c0a0458e8e476b2a62f95147; from 874b2adbed1253a11549cb9b7b912ab65fea9cf2 before e261be6f18929f2397cd54cd583a2df624c129c1; 874b2adbed1253a11549cb9b7b912ab65fea9cf2 builds before 642f33e34b969eedec334738fd5df95d2dc42742	CNA record
linux linux_kernel linux:linux_kernel	from 4.13 before 5.10.252; from 5.11 before 5.15.202; from 5.16 before 6.1.165; from 6.2 before 6.6.128; from 6.7 before 6.12.75; from 6.13 before 6.18.14; from 6.19 before 6.19.4	NVD

References

References

https://git.kernel.org/stable/c/c549dd3de4b3f6e726d1b8386d40ccf7d3abdbe4	patch
https://git.kernel.org/stable/c/3ff75cba1c98349a23a8f9333981deba1972cc11	patch
https://git.kernel.org/stable/c/2ce2334be155bd8bad6377e99984246ce4dbd08c	patch
https://git.kernel.org/stable/c/cbb9b07f88a9ef6518934c41eb3e8cf840d657d5	patch
https://git.kernel.org/stable/c/f3fbe309c9bfe1aac1e2b26543e9dc4829f3275a	patch
https://git.kernel.org/stable/c/2841bbb5a35c4449c0a0458e8e476b2a62f95147	patch
https://git.kernel.org/stable/c/e261be6f18929f2397cd54cd583a2df624c129c1	patch
https://git.kernel.org/stable/c/642f33e34b969eedec334738fd5df95d2dc42742	patch

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.