# CVE-2026-89468: power: supply: lp8788-charger: fix use-after-free on remove

> A use-after-free vulnerability in the Linux kernel lp8788-charger driver allows local attackers to cause denial of service or execute arbitrary code.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-100563, BELL-CVE-2026-89468, DEBIAN-CVE-2026-89468, GHSA-v57r-whwp-c5pf, UBUNTU-CVE-2026-89468

## What is CVE-2026-89468?

CVE-2026-89468 is an use after free vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2026-89468?


## How do I fix CVE-2026-89468?

Apply the vendor's patch.

## Is CVE-2026-89468 being exploited?

There is no known exploitation of CVE-2026-89468 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-89468 and fix it if it is affected.

What it is: CVE-2026-89468 is an use after free vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-89468 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-89468/ (Markdown: https://insights.sbomify.com/CVE-2026-89468/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-89468
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-89468
- OSV: https://osv.dev/vulnerability/CVE-2026-89468

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-89468/
Summaries are generated and may contain mistakes; the official description above is the record.