CVE-2026-45885: power: supply: cpcap-battery: Fix use-after-free in power_supply_changed()
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 2841bbb5a35c4449c0a0458e8e476b2a62f95147, 2ce2334be155bd8bad6377e99984246ce4dbd08c, 3ff75cba1c98349a23a8f9333981deba1972cc11.
Low priority for now. Upgrade to Linux Linux 2841bbb5a35c4449c0a0458e8e476b2a62f95147, 2ce2334be155bd8bad6377e99984246ce4dbd08c, 3ff75cba1c98349a23a8f9333981deba1972cc11 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 27, 2026
- Updated
- Jun 25, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- CWE-416
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.13affected
- 874b2adbed1253a11549cb9b7b912ab65fea9cf2 and later · before c549dd3de4b3f6e726d1b8386d40ccf7d3abdbe4affected · git
- 874b2adbed1253a11549cb9b7b912ab65fea9cf2 and later · before 3ff75cba1c98349a23a8f9333981deba1972cc11affected · git
- 874b2adbed1253a11549cb9b7b912ab65fea9cf2 and later · before 2ce2334be155bd8bad6377e99984246ce4dbd08caffected · git
- 874b2adbed1253a11549cb9b7b912ab65fea9cf2 and later · before cbb9b07f88a9ef6518934c41eb3e8cf840d657d5affected · git
- 874b2adbed1253a11549cb9b7b912ab65fea9cf2 and later · before f3fbe309c9bfe1aac1e2b26543e9dc4829f3275aaffected · git
- 874b2adbed1253a11549cb9b7b912ab65fea9cf2 and later · before 2841bbb5a35c4449c0a0458e8e476b2a62f95147affected · git
- 874b2adbed1253a11549cb9b7b912ab65fea9cf2 and later · before e261be6f18929f2397cd54cd583a2df624c129c1affected · git
- 874b2adbed1253a11549cb9b7b912ab65fea9cf2 and later · before 642f33e34b969eedec334738fd5df95d2dc42742affected · git
- before 4.13not affected · semver
Affected versions · NVD (7)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.13 and later · before 5.10.252
- linux linux kernel5.11 and later · before 5.15.202
- linux linux kernel5.16 and later · before 6.1.165
- linux linux kernel6.2 and later · before 6.6.128
- linux linux kernel6.7 and later · before 6.12.75
- linux linux kernel6.13 and later · before 6.18.14
- linux linux kernel6.19 and later · before 6.19.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.170-1 | 6.1.170-1 |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.18.14-1 | 6.18.14-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-45883May 27, 2026 · iio: sca3000: Fix a resource leak in sca3000_probe()22Monitor
- ← EarlierCVE-2026-45884May 27, 2026 · apparmor: avoid per-cpu hold underflow in aa_get_buffer22Monitor
- Later →CVE-2026-45887May 27, 2026 · af_unix: Fix memleak of newsk in unix_stream_connect().22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2841bbb5a35c4449c0a0458e8e476b2a62f95147 | Vendor (CNA) |
| Linux Linux | 2ce2334be155bd8bad6377e99984246ce4dbd08c | Vendor (CNA) |
| Linux Linux | 3ff75cba1c98349a23a8f9333981deba1972cc11 | Vendor (CNA) |
| Linux Linux | 642f33e34b969eedec334738fd5df95d2dc42742 | Vendor (CNA) |
| Linux Linux | c549dd3de4b3f6e726d1b8386d40ccf7d3abdbe4 | Vendor (CNA) |
| Linux Linux | cbb9b07f88a9ef6518934c41eb3e8cf840d657d5 | Vendor (CNA) |
| Linux Linux | e261be6f18929f2397cd54cd583a2df624c129c1 | Vendor (CNA) |
| Linux Linux | f3fbe309c9bfe1aac1e2b26543e9dc4829f3275a | Vendor (CNA) |
| debian:linux | 6.1.170-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2ce2334be155bd8bad6377e99984246ce4dbd08c
- git.kernel.org/stable/c/3ff75cba1c98349a23a8f9333981deba1972cc11
- git.kernel.org/stable/c/642f33e34b969eedec334738fd5df95d2dc42742
- git.kernel.org/stable/c/c549dd3de4b3f6e726d1b8386d40ccf7d3abdbe4
- git.kernel.org/stable/c/cbb9b07f88a9ef6518934c41eb3e8cf840d657d5
- git.kernel.org/stable/c/e261be6f18929f2397cd54cd583a2df624c129c1
- git.kernel.org/stable/c/f3fbe309c9bfe1aac1e2b26543e9dc4829f3275a
Vendor advisories and official records. Exploit/PoC links are deliberately left out.