CVE-2026-89467 — power: supply: qcom_battmgr: fix use-after-free
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux | ≥ 29e8142b5623b5949587bcc4f591c4e6595c4aca and < 77fefca305db44b0edd3fcdb52d781771c1ce366≥ 29e8142b5623b5949587bcc4f591c4e6595c4aca and < 06618447029c6dddaa02f6e9528efe5dd49fc329≥ 29e8142b5623b5949587bcc4f591c4e6595c4aca and < 49fbcd3da2958159370d25dafbf736e654a4d59b≥ 29e8142b5623b5949587bcc4f591c4e6595c4aca and < 4e40befedfc8ed86f44e1f81df92d13c149c9f8dversion 6.3≥ 29e8142b5623b5949587bcc4f591c4e6595c4aca and < 35964ed01e10b61a30066b0c568aa0e0e8fb6432 | Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 23, 2026 · 8 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 19, 2026 – Oct 21, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
7 on the record
- nvd.nist.gov/vuln/detail/CVE-2026-89467
- git.kernel.org/stable/c/4e40befedfc8ed86f44e1f81df92d13c149c9f8d
- git.kernel.org/stable/c/77fefca305db44b0edd3fcdb52d781771c1ce366
- git.kernel.org/stable/c/49fbcd3da2958159370d25dafbf736e654a4d59b
- github.com/advisories/GHSA-6hqf-cg9r-x89w
- git.kernel.org/stable/c/35964ed01e10b61a30066b0c568aa0e0e8fb6432
- git.kernel.org/stable/c/06618447029c6dddaa02f6e9528efe5dd49fc329
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99087 dm-integrity: fix NULL pointer dereference when the 'R' flag is used 1d
- Unknown CVE-2026-99086 dm-integrity: validate the superblock on resume 1d
- Unknown CVE-2026-99084 readdir: take no inode lock on an immutable directory 1d
- Unknown CVE-2026-99080 fs: Free any excess xarray nodes in clear_inode() 1d
- Unknown CVE-2026-99085 sched_ext: Fix CPU hotplug hang when a dying CPU's tasks sit in the BPF scheduler 1d
- Critical CVE-2026-99079 net/mlx5e: Prevent stale XSK buffer release on refill retry 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-89467 is "power: supply: qcom_battmgr: fix use-after-free", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.