# CVE-2026-89461: power: supply: max17040: synchronize work cancellation on suspend

> A race condition in the Linux kernel max17040 driver during system suspend can cause denial of service by allowing polling callbacks to access hardware after suspension.

- **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:** 19 Oct 2026
- **Also known as:** AZL-100560, BELL-CVE-2026-89461, DEBIAN-CVE-2026-89461, GHSA-5fpq-2c4w-2f7x, UBUNTU-CVE-2026-89461

## What is CVE-2026-89461?

CVE-2026-89461 is a 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: max17040: synchronize work cancellation on suspend

max17040_work() requeues itself after every poll. cancel_delayed_work()
only cancels a pending instance and does not wait for a callback that is
already running.

If system suspend races with the polling callback, the callback can
continue accessing the fuel gauge and requeue itself after the suspend
callback returns.

Use cancel_delayed_work_sync() to ensure polling is quiesced before
suspend completes.

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


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

Apply the vendor's patch.

## Is CVE-2026-89461 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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