In the Linux kernel, the following vulnerability has been resolved: power: supply: cpcap-battery: Fix missing nvmem_device_put() causing reference… (CVE-2026-72214)
A vulnerability in the Linux kernel's cpcap-battery driver caused a reference leak due to a missing call to nvmem_device_put() after obtaining an nvmem device reference. This leak occurs in the function cpcap_battery_detect_battery_type() on both success and read-failure paths, potentially leading to a permanent reference leak that prevents the device from being freed. The issue was found by code review and has been resolved.
AI Analysis
Technical Summary
The Linux kernel's power supply driver for cpcap-battery had a defect where the reference to an nvmem device obtained via nvmem_device_find() was not released with nvmem_device_put() on success or failure paths in cpcap_battery_detect_battery_type(). This caused a permanent reference leak, which could be compounded by the driver's retry logic on subsequent battery property reads, preventing the nvmem device from ever being freed. The vulnerability was identified through code review and has been fixed.
Potential Impact
The vulnerability causes a permanent reference leak in the kernel driver, which could lead to resource exhaustion or instability in the affected system. There is no indication of direct exploitation or escalation of privileges. No known exploits are reported in the wild.
Mitigation Recommendations
The vulnerability has been resolved in the Linux kernel by adding the missing nvmem_device_put() call to properly release the nvmem device reference. Users should update to the fixed kernel version containing this patch. Patch status is not explicitly confirmed in the provided data; check the vendor advisory or Linux kernel release notes for the exact fixed version and apply the update accordingly.
In the Linux kernel, the following vulnerability has been resolved: power: supply: cpcap-battery: Fix missing nvmem_device_put() causing reference… (CVE-2026-72214)
Description
A vulnerability in the Linux kernel's cpcap-battery driver caused a reference leak due to a missing call to nvmem_device_put() after obtaining an nvmem device reference. This leak occurs in the function cpcap_battery_detect_battery_type() on both success and read-failure paths, potentially leading to a permanent reference leak that prevents the device from being freed. The issue was found by code review and has been resolved.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's power supply driver for cpcap-battery had a defect where the reference to an nvmem device obtained via nvmem_device_find() was not released with nvmem_device_put() on success or failure paths in cpcap_battery_detect_battery_type(). This caused a permanent reference leak, which could be compounded by the driver's retry logic on subsequent battery property reads, preventing the nvmem device from ever being freed. The vulnerability was identified through code review and has been fixed.
Potential Impact
The vulnerability causes a permanent reference leak in the kernel driver, which could lead to resource exhaustion or instability in the affected system. There is no indication of direct exploitation or escalation of privileges. No known exploits are reported in the wild.
Mitigation Recommendations
The vulnerability has been resolved in the Linux kernel by adding the missing nvmem_device_put() call to properly release the nvmem device reference. Users should update to the fixed kernel version containing this patch. Patch status is not explicitly confirmed in the provided data; check the vendor advisory or Linux kernel release notes for the exact fixed version and apply the update accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-m52x-f225-mf2c
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-72214"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a808b73bf8831d5394fe0d6
Added to database: 08/15/2026, 15:53:23 UTC
Last enriched: 08/15/2026, 16:47:27 UTC
Last updated: 08/16/2026, 00:41:15 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.