CVE-2026-72214

power: supply: cpcap-battery: Fix missing nvmem_device_put() causing reference leak

N/A
Published: August 15, 2026 at 05:54 AM UTC
Updated: August 17, 2026 at 06:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: power: supply: cpcap-battery: Fix missing nvmem_device_put() causing reference leak In cpcap_battery_detect_battery_type(), the reference to an nvmem device obtained via nvmem_device_find() is not released with nvmem_device_put() on the success or read-failure paths, causing a permanent reference leak. The driver’s retry logic on subsequent battery property reads can compound this leak, preventing the nvmem device from ever being freed. Found by code review.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.18 ≤ v < 6.1.1785.18 ≤ v < 6.12.975.18 ≤ v < 6.18.405.18 ≤ v < 6.6.1455.18 ≤ v < 7.1.55.18 ≤ v < 7.25.18fd46821e85de90fb5b7356251164af4815b6e3f6
Vendor states this is fixed in 700c225d829a1256b59053c34a1a9d1a6ab70b09 (fixed)
Vendor states this is fixed in a2c14ff63e0e02e3c832385e523e9cc81301171c (fixed)
Vendor states this is fixed in a3d81de441233a92ec21469cd0c4eb3c26b95cd8 (fixed)
Vendor states this is fixed in b56a5cbf8f1f1a5740f1137c89b14d0373309d8d (fixed)
Vendor states this is fixed in deaf6b3f8187231ad8f7770b10ed0be2cd47e9b2 (fixed)
Vendor states this is fixed in fc65520fe0781a1ff46631f111e07b4a1c677b96 (fixed)
Vendor states this is fixed in 5.18 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card