System crash via sbs-battery IRQ lifecycle race
Published May 27, 2026 · Updated May 27, 2026
Use-after-free in the Linux Kernel sbs-battery driver allows local users to crash the system or corrupt kernel memory during teardown. In sbs-battery.c, the driver requests its managed IRQ before registering the managed power_supply handle, so reverse-order cleanup frees the handle while the IRQ handler remains callable. The race requires the sbs-battery driver and interrupt timing during probe or removal; a winning interrupt passes a freed or uninitialized handle to power_supply_changed().
Summary
What happened
Use-after-free in the Linux Kernel sbs-battery driver allows local users to crash the system or corrupt kernel memory during teardown. In sbs-battery.c, the driver requests its managed IRQ before registering the managed power_supply handle, so reverse-order cleanup frees the handle while the IRQ handler remains callable. The race requires the sbs-battery driver and interrupt timing during probe or removal; a winning interrupt passes a freed or uninitialized handle to power_supply_changed().
The record
- CVE
- CVE-2026-45916
- 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=4.9
- Affected versionversion=d2cec82c28802da31596b395ad292cb8f132fd63 <14d4dee5d8fb361bfff275832087254beab66d72
- Affected versionversion=d2cec82c28802da31596b395ad292cb8f132fd63 <2078830c32d1e49ac942c6f8c21f35c806ae5e94
- Affected versionversion=d2cec82c28802da31596b395ad292cb8f132fd63 <8010b745b436c3e1ca5dd960aa29fa3e0f6d8841
- Affected versionversion=d2cec82c28802da31596b395ad292cb8f132fd63 <82d3eb97a976c9d56bb92b241397610e57a9c629
- Affected versionversion=d2cec82c28802da31596b395ad292cb8f132fd63 <861dda7a9074c0ff67788928165ae39d7f647491
- Affected versionversion=d2cec82c28802da31596b395ad292cb8f132fd63 <8d59cf3887fbabacef53bfba473e33e8a8d9d07b
- Affected versionversion=d2cec82c28802da31596b395ad292cb8f132fd63 <ca7dd71773e4e050b0fb98768b7eae60f8d1f38b
- Affected versionversion=d2cec82c28802da31596b395ad292cb8f132fd63 <f1f472b14ad56104ba228b8fbec60d5b21829913
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