CVE-2026-89468: power: supply: lp8788-charger: fix use-after-free on remove
Noroxi assessment
Priority: Monitor (action score 0/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.17% (FIRST EPSS).
- Fixed version: Linux Linux 4e3d3923976a986cc3cf960d13f1264cea8a9bba, 831c29a12d560f8a3225f43050b3fbb5dfd79c66, 8758fe39a993f86998c8071826150b8859902497.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 4e3d3923976a986cc3cf960d13f1264cea8a9bba, 831c29a12d560f8a3225f43050b3fbb5dfd79c66, 8758fe39a993f86998c8071826150b8859902497 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: lp8788-charger: fix use-after-free on remove lp8788_charger_remove() flushes charger_work before unregistering the IRQs. An IRQ thread can queue charger_work after flush_work() has returned. The work can then run after devres frees pchg and dereference it in lp8788_charger_event(). Unregister the IRQs first. free_irq() waits for any running threaded handler, so no handler can queue more work afterwards. Then use cancel_work_sync() to cancel pending work or wait for running work to finish. This issue was found by an in-house static analysis tool.
- Published
- Sep 11, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- 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.
—
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
- 3.7affected
- 98a2766493589c18c327ae3dad5243b53fcb5f70 and later · before 8758fe39a993f86998c8071826150b8859902497affected · git
- 98a2766493589c18c327ae3dad5243b53fcb5f70 and later · before 4e3d3923976a986cc3cf960d13f1264cea8a9bbaaffected · git
- 98a2766493589c18c327ae3dad5243b53fcb5f70 and later · before 88d8eadfad5d9ff967e74090152940bcfa27df69affected · git
- 98a2766493589c18c327ae3dad5243b53fcb5f70 and later · before b3aa1e9509e1b0a863353356d617fb45d1b6250aaffected · git
- 98a2766493589c18c327ae3dad5243b53fcb5f70 and later · before b4eb6a056b441ba0caedfbfc42cec501acf12f67affected · git
- 98a2766493589c18c327ae3dad5243b53fcb5f70 and later · before 831c29a12d560f8a3225f43050b3fbb5dfd79c66affected · git
- before 3.7not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
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.192-1 | 6.1.192-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-89466Sep 11, 2026 · power: supply: qcom_battmgr: terminate the strings from firmware30Monitor
- ← EarlierCVE-2026-89467Sep 11, 2026 · power: supply: qcom_battmgr: fix use-after-free0Monitor
- Later →CVE-2026-89469Sep 11, 2026 · power: supply: lp8727: fix use-after-free in lp8727_release_irq()33Monitor
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 | 4e3d3923976a986cc3cf960d13f1264cea8a9bba | Vendor (CNA) |
| Linux Linux | 831c29a12d560f8a3225f43050b3fbb5dfd79c66 | Vendor (CNA) |
| Linux Linux | 8758fe39a993f86998c8071826150b8859902497 | Vendor (CNA) |
| Linux Linux | 88d8eadfad5d9ff967e74090152940bcfa27df69 | Vendor (CNA) |
| Linux Linux | b3aa1e9509e1b0a863353356d617fb45d1b6250a | Vendor (CNA) |
| Linux Linux | b4eb6a056b441ba0caedfbfc42cec501acf12f67 | Vendor (CNA) |
| debian:linux | 6.1.192-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1085 · Sep 14, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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 (5 more)Show less
- git.kernel.org/stable/c/831c29a12d560f8a3225f43050b3fbb5dfd79c66
- git.kernel.org/stable/c/8758fe39a993f86998c8071826150b8859902497
- git.kernel.org/stable/c/88d8eadfad5d9ff967e74090152940bcfa27df69
- git.kernel.org/stable/c/b3aa1e9509e1b0a863353356d617fb45d1b6250a
- git.kernel.org/stable/c/b4eb6a056b441ba0caedfbfc42cec501acf12f67
Vendor advisories and official records. Exploit/PoC links are deliberately left out.