# CVE-2026-89469: power: supply: lp8727: fix use-after-free in lp8727_release_irq()

> A use-after-free in the Linux kernel lp8727 power supply driver allows attackers to cause denial of service or execute code via race conditions during device removal.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 19 Oct 2026
- **Also known as:** AZL-100229, BELL-CVE-2026-89469, DEBIAN-CVE-2026-89469, GHSA-69w5-534x-wxxj, UBUNTU-CVE-2026-89469

## What is CVE-2026-89469?

CVE-2026-89469 is a high-severity 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: lp8727: fix use-after-free in lp8727_release_irq()

lp8727_isr_func(), the threaded IRQ handler, is the only caller that arms
pchg->work via schedule_delayed_work().  lp8727_release_irq() currently
cancels the work before freeing the IRQ, so an IRQ delivered in between
can re-arm the work through the threaded handler.  After .remove returns
the devm layer frees pchg while lp8727_delayed_func() may still run and
dereference it.

Free the IRQ first so the threaded handler is quiesced and can no longer
queue work, then cancel the delayed work to drain the final generation.

This issue was found by an in-house static analysis tool.

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


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

Apply the vendor's patch.

## Is CVE-2026-89469 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89469 is a high-severity 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-89469 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-89469/ (Markdown: https://insights.sbomify.com/CVE-2026-89469/index.md)
```

## Sources

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

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