linux-cve-announce - CVE-2025-38275: phy: qcom-qmp-usb: Fix an NULL vs IS

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: <2025071008-CVE-2025-38275-4db0@gregkh>
Date: Thu, 10 Jul 2025 09:42:16 +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-38275: phy: qcom-qmp-usb: Fix an NULL vs IS_ERR() bug

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

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

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

phy: qcom-qmp-usb: Fix an NULL vs IS_ERR() bug

The qmp_usb_iomap() helper function currently returns the raw result of
devm_ioremap() for non-exclusive mappings. Since devm_ioremap() may return
a NULL pointer and the caller only checks error pointers with IS_ERR(),
NULL could bypass the check and lead to an invalid dereference.

Fix the issue by checking if devm_ioremap() returns NULL. When it does,
qmp_usb_iomap() now returns an error pointer via IOMEM_ERR_PTR(-ENOMEM),
ensuring safe and consistent error handling.

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


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

	Issue introduced in 6.1 with commit a5d6b1ac56cbd6b5850a3a54e35f1cb71e8e8cdd and fixed in 6.1.142 with commit 0b979a409e40457ca1b5cb48755d1f34eee58805
	Issue introduced in 6.1 with commit a5d6b1ac56cbd6b5850a3a54e35f1cb71e8e8cdd and fixed in 6.6.94 with commit 127dfb4f1c5a2b622039c5d203f321380ea36665
	Issue introduced in 6.1 with commit a5d6b1ac56cbd6b5850a3a54e35f1cb71e8e8cdd and fixed in 6.12.34 with commit 5072c1749197fc28b27d7efc0d80320d7cac9572
	Issue introduced in 6.1 with commit a5d6b1ac56cbd6b5850a3a54e35f1cb71e8e8cdd and fixed in 6.15.3 with commit 0c33117f00c8c5363c22676931b22ae5041f7603
	Issue introduced in 6.1 with commit a5d6b1ac56cbd6b5850a3a54e35f1cb71e8e8cdd and fixed in 6.16-rc1 with commit d14402a38c2d868cacb1facaf9be908ca6558e59
	Issue introduced in 5.15.93 with commit 368ea32e0ad0335bdf3180067875a928e35387c6

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-38275
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/phy/qualcomm/phy-qcom-qmp-usb.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/0b979a409e40457ca1b5cb48755d1f34eee58805
	https://git.kernel.org/stable/c/127dfb4f1c5a2b622039c5d203f321380ea36665
	https://git.kernel.org/stable/c/5072c1749197fc28b27d7efc0d80320d7cac9572
	https://git.kernel.org/stable/c/0c33117f00c8c5363c22676931b22ae5041f7603
	https://git.kernel.org/stable/c/d14402a38c2d868cacb1facaf9be908ca6558e59