CVE-2026-89467 json
power: supply: qcom_battmgr: fix use-after-free
published 2026-09-11 58 d ago modified 2026-10-21 18 d ago also EUVD-2026-76373
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 6.6.160, 6.12.112, 6.18.50, 7.2.4, 7.3
- linux Debian 13 6.12.113-1
- linux Debian 14 7.2.6-1
- linux-6.12 Debian 12 6.12.113-1~deb12u1
debian advisories DEBIAN-CVE-2026-89467
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
- linux-ibm Ubuntu 26.04 LTS 7.0.0-1017.17
- linux-riscv Ubuntu 26.04 LTS 7.0.0-42.42.1
- linux-oracle Ubuntu 26.04 LTS 7.0.0-1015.16
- linux-hwe-7.0 Ubuntu 24.04 LTS 7.0.0-42.42~24.04.1
- linux-oem-7.0 Ubuntu 26.04 LTS 7.0.0-1017.17
ubuntu advisories UBUNTU-CVE-2026-89467
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source openSUSE Tumbleweed 7.2.7-1.1
opensuse advisories openSUSE-SU-2026:11880-1
- git.kernel.org/stable/c/35964ed01e10b61a30066b0c568aa0e0e8fb6432 commit
- git.kernel.org/stable/c/77fefca305db44b0edd3fcdb52d781771c1ce366 commit
- git.kernel.org/stable/c/06618447029c6dddaa02f6e9528efe5dd49fc329 commit
- git.kernel.org/stable/c/49fbcd3da2958159370d25dafbf736e654a4d59b commit
- git.kernel.org/stable/c/4e40befedfc8ed86f44e1f81df92d13c149c9f8d commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-89467 updated cvss 5.5
kernel: power: supply: qcom_battmgr: fix use-after-free
-
Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/35964ed01e10b61a30066b0c568aa0e0e8fb6432
- git.kernel.org /stable/c/77fefca305db44b0edd3fcdb52d781771c1ce366
- git.kernel.org /stable/c/06618447029c6dddaa02f6e9528efe5dd49fc329
- git.kernel.org /stable/c/49fbcd3da2958159370d25dafbf736e654a4d59b
- git.kernel.org /stable/c/4e40befedfc8ed86f44e1f81df92d13c149c9f8d
Sources
- CVE List CVE-2026-89467
- NVD CVE-2026-89467
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.