Skip to main content
VulnerabilityPublished Updated

CVE-2026-89467: Linux kernel · power: supply: qcom_battmgr: fix use-after-free

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in 06618447029c6dddaa02f6e9528efe5dd49fc329 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 06618447029c6dddaa02f6e9528efe5dd49fc329, 35964ed01e10b61a30066b0c568aa0e0e8fb6432, 77fefca305db44b0edd3fcdb52d781771c1ce366 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 29e8142b5623b5949587bcc4f591c4e6595c4aca, < 06618447029c6dddaa02f6e9528efe5dd49fc329
Fixed in
  • 06618447029c6dddaa02f6e9528efe5dd49fc329
LinuxLinuxAffected
  • ≥ 29e8142b5623b5949587bcc4f591c4e6595c4aca, < 35964ed01e10b61a30066b0c568aa0e0e8fb6432
Fixed in
  • 35964ed01e10b61a30066b0c568aa0e0e8fb6432
LinuxLinuxAffected
  • ≥ 29e8142b5623b5949587bcc4f591c4e6595c4aca, < 77fefca305db44b0edd3fcdb52d781771c1ce366
Fixed in
  • 77fefca305db44b0edd3fcdb52d781771c1ce366
LinuxLinuxAffected
  • ≥ 29e8142b5623b5949587bcc4f591c4e6595c4aca, < 49fbcd3da2958159370d25dafbf736e654a4d59b
Fixed in
  • 49fbcd3da2958159370d25dafbf736e654a4d59b
LinuxLinuxAffected
  • ≥ 29e8142b5623b5949587bcc4f591c4e6595c4aca, < 4e40befedfc8ed86f44e1f81df92d13c149c9f8d
Fixed in
  • 4e40befedfc8ed86f44e1f81df92d13c149c9f8d
LinuxLinuxAffected
  • =6.3
Fixed in–

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.

References

Community reviews

Loading reviews…