linux-cve-announce - CVE-2025-38634: power: supply: cpcap-charger: Fix null check for power_supply_get_by

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025082233-CVE-2025-38634-d884@gregkh>
Date: Fri, 22 Aug 2025 18:00:43 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38634: power: supply: cpcap-charger: Fix null check for power_supply_get_by_name

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

power: supply: cpcap-charger: Fix null check for power_supply_get_by_name

In the cpcap_usb_detect() function, the power_supply_get_by_name()
function may return `NULL` instead of an error pointer.
To prevent potential null pointer dereferences, Added a null check.

The Linux kernel CVE team has assigned CVE-2025-38634 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.14 with commit eab4e6d953c1059a30ac0f15826abc7dd2374d3c and fixed in 6.1.148 with commit a2436263144980cc99a9860c7b43335847afbe53
	Issue introduced in 5.14 with commit eab4e6d953c1059a30ac0f15826abc7dd2374d3c and fixed in 6.6.102 with commit 8e9bdb563916287ba1b4258812434e0585ac6d00
	Issue introduced in 5.14 with commit eab4e6d953c1059a30ac0f15826abc7dd2374d3c and fixed in 6.12.42 with commit f642500aa7ed93d2606e4f929244cce9c7467b3a
	Issue introduced in 5.14 with commit eab4e6d953c1059a30ac0f15826abc7dd2374d3c and fixed in 6.15.10 with commit 9784d832d7c103539cd9afb376534eaa35815d3d
	Issue introduced in 5.14 with commit eab4e6d953c1059a30ac0f15826abc7dd2374d3c and fixed in 6.16.1 with commit 27001e4f146624c4b3389b029bdc0f8049819560
	Issue introduced in 5.14 with commit eab4e6d953c1059a30ac0f15826abc7dd2374d3c and fixed in 6.17-rc1 with commit d9fa3aae08f99493e67fb79413c0e95d30fca5e9

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2025-38634
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/power/supply/cpcap-charger.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/a2436263144980cc99a9860c7b43335847afbe53
	https://git.kernel.org/stable/c/8e9bdb563916287ba1b4258812434e0585ac6d00
	https://git.kernel.org/stable/c/f642500aa7ed93d2606e4f929244cce9c7467b3a
	https://git.kernel.org/stable/c/9784d832d7c103539cd9afb376534eaa35815d3d
	https://git.kernel.org/stable/c/27001e4f146624c4b3389b029bdc0f8049819560
	https://git.kernel.org/stable/c/d9fa3aae08f99493e67fb79413c0e95d30fca5e9