PatchSiren cyber security CVE debrief
CVE-2026-89467 Linux CVE debrief
A use-after-free vulnerability was found in the Linux kernel's qcom_battmgr module. The qcom_battmgr_pdr_notify() function queues enable_work when the PMIC GLINK service comes up, and the worker recovers battmgr through container_of() to issue firmware requests. However, the PMIC GLINK client stays on the client list until its devres release action runs, allowing a PDR notification to keep queueing the work, and a pending or running worker can access battmgr after devres frees it.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-11
- Original CVE updated
- 2026-09-11
- Advisory published
- 2026-09-11
- Advisory updated
- 2026-09-11
Who should care
Linux kernel developers and maintainers, Linux distribution maintainers, affected system administrators, security teams, and vulnerability management teams should assess exposure and prioritize verification of affected versions and deployments, review Linux kernel source code and documentation for qcom_battmgr module, and verify affected versions and deployments.
Why it matters
A use-after-free vulnerability was found in the Linux kernel's qcom_battmgr module, allowing a PDR notification to keep queueing the work, and a pending or running worker can access battmgr after devres frees it.
- Verify affected versions and deployments
- Assess exposure and prioritize remediation
- Review Linux kernel source code and documentation for qcom_battmgr module
Technical summary
The qcom_battmgr_pdr_notify() function queues enable_work when the PMIC GLINK service comes up, and the worker recovers battmgr through container_of() to issue firmware requests. However, the PMIC GLINK client stays on the client list until its devres release action runs, allowing a PDR notification to keep queueing the work, and a pending or running worker can access battmgr after devres frees it.
Defensive priority
Linux kernel developers and maintainers should assess exposure and prioritize verification of affected versions and deployments.
Recommended defensive actions
- Review Linux kernel source code and documentation for qcom_battmgr module
- Verify affected versions and deployments
- Assess exposure and prioritize remediation
- Review compensating controls for exposed systems
- Check relevant monitoring, detection, and logs for exposed assets
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
Evidence notes
The issue was found by an in-house static analysis tool. The CVE record and NVD entry provide limited information about the vulnerability. Linux kernel developers and maintainers should verify affected versions and deployments, assess exposure, and prioritize remediation. The qcom_battmgr_pdr_notify() function queues enable_work when the PMIC GLINK service comes up, and the worker recovers battmgr through container_of() to issue firmware requests.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-89467 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-89467
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-89467 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-89467
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/06618447029c6dddaa02f6e9528efe5dd49fc329
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/49fbcd3da2958159370d25dafbf736e654a4d59b
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/4e40befedfc8ed86f44e1f81df92d13c149c9f8d
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.