Kernel crash via bq25980 IRQ teardown race
Published May 27, 2026 · Updated May 27, 2026
Use-after-free in the Linux kernel bq25980 power-supply driver allows local users to crash the system during device removal. The driver requests its managed IRQ before registering the managed power_supply handle, so reverse teardown can free the handle while the IRQ remains active. An interrupt during removal then passes the freed handle to power_supply_changed, causing a kernel crash or silent memory corruption; a probe-time interrupt can also use the handle before initialization.
Summary
What happened
Use-after-free in the Linux kernel bq25980 power-supply driver allows local users to crash the system during device removal. The driver requests its managed IRQ before registering the managed power_supply handle, so reverse teardown can free the handle while the IRQ remains active. An interrupt during removal then passes the freed handle to power_supply_changed, causing a kernel crash or silent memory corruption; a probe-time interrupt can also use the handle before initialization.
The record
- CVE
- CVE-2026-45879
- Published
- May 27, 2026
- Updated
- May 27, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 27, 2026CVE publishedPublication date reported by the CVE source.
- May 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5069185fc18e810715a91d80fcd075e03add600c <03d1e4ee4e6aa6d2966e883e4ca0e5be73bf1b7c
- Affected versionversion=5069185fc18e810715a91d80fcd075e03add600c <0560a4b09c92e2ecaa883965cf6f9ca51c158ff9
- Affected versionversion=5069185fc18e810715a91d80fcd075e03add600c <0de95d29d847c6217b7d5845e24a71a4aee7b359
- Affected versionversion=5069185fc18e810715a91d80fcd075e03add600c <16875e3b7bc9e59bfa0acaf1e43f275a6f42a30f
- Affected versionversion=5069185fc18e810715a91d80fcd075e03add600c <4aeaf03c17260415c2fdd55992f9ad4188d5455a
- Affected versionversion=5069185fc18e810715a91d80fcd075e03add600c <5f0b1cb41906e86b64bf69f5ededb83b0d757c27
- Affected versionversion=5069185fc18e810715a91d80fcd075e03add600c <86f93dfb23f5bf4f285c4256a7e909d222f7de56
- Affected versionversion=5069185fc18e810715a91d80fcd075e03add600c <abea607ff2f62f4c0a5fb29f7fbdaaab163276a4
- Affected versionversion=5.10
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo