Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Fixed version: Linux Linux 700c225d829a1256b59053c34a1a9d1a6ab70b09, a2c14ff63e0e02e3c832385e523e9cc81301171c, a3d81de441233a92ec21469cd0c4eb3c26b95cd8.

Low priority for now. Upgrade to Linux Linux 700c225d829a1256b59053c34a1a9d1a6ab70b09, a2c14ff63e0e02e3c832385e523e9cc81301171c, a3d81de441233a92ec21469cd0c4eb3c26b95cd8 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Aug 15, 2026
Updated
Aug 17, 2026
EPSS
0.2% · 11th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-72214

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.18affected
    • fd46821e85de90fb5b7356251164af4815b6e3f6 and later · before fc65520fe0781a1ff46631f111e07b4a1c677b96affected · git
    • fd46821e85de90fb5b7356251164af4815b6e3f6 and later · before 700c225d829a1256b59053c34a1a9d1a6ab70b09affected · git
    • fd46821e85de90fb5b7356251164af4815b6e3f6 and later · before deaf6b3f8187231ad8f7770b10ed0be2cd47e9b2affected · git
    • fd46821e85de90fb5b7356251164af4815b6e3f6 and later · before a3d81de441233a92ec21469cd0c4eb3c26b95cd8affected · git
    • fd46821e85de90fb5b7356251164af4815b6e3f6 and later · before b56a5cbf8f1f1a5740f1137c89b14d0373309d8daffected · git
    • fd46821e85de90fb5b7356251164af4815b6e3f6 and later · before a2c14ff63e0e02e3c832385e523e9cc81301171caffected · git
    • before 5.18not affected · semver
    • 6.1.178 and later · up to and including 6.1.*not affected · semver
    • 6.6.145 and later · up to and including 6.6.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.5-17.1.5-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-72211Aug 15, 2026 · ntfs: grow index root value before reparent header update
    39Monitor
  • ← EarlierCVE-2026-72212Aug 15, 2026 · mm/memory_hotplug: fix incorrect altmap passing in error path
    0Monitor
  • Later →CVE-2026-72215Aug 15, 2026 · MIPS: DEC: Ensure 32-bit stack location for o32 prom_printf()
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux700c225d829a1256b59053c34a1a9d1a6ab70b09Vendor (CNA)
Linux Linuxa2c14ff63e0e02e3c832385e523e9cc81301171cVendor (CNA)
Linux Linuxa3d81de441233a92ec21469cd0c4eb3c26b95cd8Vendor (CNA)
Linux Linuxb56a5cbf8f1f1a5740f1137c89b14d0373309d8dVendor (CNA)
Linux Linuxdeaf6b3f8187231ad8f7770b10ed0be2cd47e9b2Vendor (CNA)
Linux Linuxfc65520fe0781a1ff46631f111e07b4a1c677b96Vendor (CNA)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records