Kernel resource retention via unreleased nvmem reference
Published Aug 15, 2026 · Updated Aug 15, 2026
A reference leak in the Linux kernel CPCAP battery driver allows local users to retain nvmem device references through battery reads. cpcap_battery_detect_battery_type() obtains an nvmem device with nvmem_device_find() but omits nvmem_device_put() on successful and failed reads. The condition requires the CPCAP battery driver and compatible battery hardware; retrying property reads compounds the permanent leak, with no reported data access or code execution.
Summary
What happened
A reference leak in the Linux kernel CPCAP battery driver allows local users to retain nvmem device references through battery reads. cpcap_battery_detect_battery_type() obtains an nvmem device with nvmem_device_find() but omits nvmem_device_put() on successful and failed reads. The condition requires the CPCAP battery driver and compatible battery hardware; retrying property reads compounds the permanent leak, with no reported data access or code execution.
The record
- CVE
- CVE-2026-72214
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.18
- Affected versionversion=fd46821e85de90fb5b7356251164af4815b6e3f6 <700c225d829a1256b59053c34a1a9d1a6ab70b09
- Affected versionversion=fd46821e85de90fb5b7356251164af4815b6e3f6 <a2c14ff63e0e02e3c832385e523e9cc81301171c
- Affected versionversion=fd46821e85de90fb5b7356251164af4815b6e3f6 <a3d81de441233a92ec21469cd0c4eb3c26b95cd8
- Affected versionversion=fd46821e85de90fb5b7356251164af4815b6e3f6 <b56a5cbf8f1f1a5740f1137c89b14d0373309d8d
- Affected versionversion=fd46821e85de90fb5b7356251164af4815b6e3f6 <deaf6b3f8187231ad8f7770b10ed0be2cd47e9b2
- Affected versionversion=fd46821e85de90fb5b7356251164af4815b6e3f6 <fc65520fe0781a1ff46631f111e07b4a1c677b96
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo