CVE-2026-89468: Linux kernel · power: supply: lp8788-charger: fix use-after-free on remove
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in b4eb6a056b441ba0caedfbfc42cec501acf12f67 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 19:46 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in b4eb6a056b441ba0caedfbfc42cec501acf12f67, b3aa1e9509e1b0a863353356d617fb45d1b6250a, 831c29a12d560f8a3225f43050b3fbb5dfd79c66 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 11 Sep 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.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in specific Linux kernel commits. Users and administrators should update to the fixed kernel versions containing the patches identified by the commit hashes provided. No additional mitigation is required beyond applying the official fix.
Description
A use-after-free vulnerability was identified and fixed in the Linux kernel's lp8788-charger power supply driver. The issue involved improper ordering of IRQ unregistration and work cancellation, which could lead to a use-after-free condition when the charger work was queued after resources were freed. The fix involves unregistering IRQs before canceling work to prevent further queuing and ensure safe resource cleanup.
References
- git.kernel.org/stable/c/4e3d3923976a986cc3cf960d13f1264cea8a9bba (opens in a new tab)
- git.kernel.org/stable/c/88d8eadfad5d9ff967e74090152940bcfa27df69 (opens in a new tab)
- git.kernel.org/stable/c/b3aa1e9509e1b0a863353356d617fb45d1b6250a (opens in a new tab)
- git.kernel.org/stable/c/b4eb6a056b441ba0caedfbfc42cec501acf12f67 (opens in a new tab)
- git.kernel.org/stable/c/831c29a12d560f8a3225f43050b3fbb5dfd79c66 (opens in a new tab)