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: <2025070331-CVE-2025-38134-cbff@gregkh>
Date: Thu,  3 Jul 2025 10:35:51 +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-38134: usb: acpi: Prevent null pointer dereference in usb_acpi_add_usb4_devlink()

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

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

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

usb: acpi: Prevent null pointer dereference in usb_acpi_add_usb4_devlink()

As demonstrated by the fix for update_port_device_state,
commit 12783c0b9e2c ("usb: core: Prevent null pointer dereference in update_port_device_state"),
usb_hub_to_struct_hub() can return NULL in certain scenarios,
such as during hub driver unbind or teardown race conditions,
even if the underlying usb_device structure exists.

Plus, all other places that call usb_hub_to_struct_hub() in the same file
do check for NULL return values.

If usb_hub_to_struct_hub() returns NULL, the subsequent access to
hub->ports[udev->portnum - 1] will cause a null pointer dereference.

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


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

	Issue introduced in 6.12 with commit f1bfb4a6fed64de1771b43a76631942279851744 and fixed in 6.12.34 with commit 8fa544bff8466062e42949c93f3e528f4be5624b
	Issue introduced in 6.12 with commit f1bfb4a6fed64de1771b43a76631942279851744 and fixed in 6.15.3 with commit e3d530173b70514d4390a94f9f979acad689b70a
	Issue introduced in 6.12 with commit f1bfb4a6fed64de1771b43a76631942279851744 and fixed in 6.16-rc1 with commit 73fb0ec9436ae87bcae067ce35d6cdd72bade86c

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-38134
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/usb/core/usb-acpi.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/8fa544bff8466062e42949c93f3e528f4be5624b
	https://git.kernel.org/stable/c/e3d530173b70514d4390a94f9f979acad689b70a
	https://git.kernel.org/stable/c/73fb0ec9436ae87bcae067ce35d6cdd72bade86c

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ