linux-cve-announce - CVE-2025-37916: pds_core: remove write-after-free of client

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: <2025052001-CVE-2025-37916-55c4@gregkh>
Date: Tue, 20 May 2025 17:22:13 +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-37916: pds_core: remove write-after-free of client_id

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

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

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

pds_core: remove write-after-free of client_id

A use-after-free error popped up in stress testing:

[Mon Apr 21 21:21:33 2025] BUG: KFENCE: use-after-free write in pdsc_auxbus_dev_del+0xef/0x160 [pds_core]
[Mon Apr 21 21:21:33 2025] Use-after-free write at 0x000000007013ecd1 (in kfence-#47):
[Mon Apr 21 21:21:33 2025]  pdsc_auxbus_dev_del+0xef/0x160 [pds_core]
[Mon Apr 21 21:21:33 2025]  pdsc_remove+0xc0/0x1b0 [pds_core]
[Mon Apr 21 21:21:33 2025]  pci_device_remove+0x24/0x70
[Mon Apr 21 21:21:33 2025]  device_release_driver_internal+0x11f/0x180
[Mon Apr 21 21:21:33 2025]  driver_detach+0x45/0x80
[Mon Apr 21 21:21:33 2025]  bus_remove_driver+0x83/0xe0
[Mon Apr 21 21:21:33 2025]  pci_unregister_driver+0x1a/0x80

The actual device uninit usually happens on a separate thread
scheduled after this code runs, but there is no guarantee of order
of thread execution, so this could be a problem.  There's no
actual need to clear the client_id at this point, so simply
remove the offending code.

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


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

	Issue introduced in 6.4 with commit 10659034c622738bc1bfab8a76fc576c52d5acce and fixed in 6.6.90 with commit 9b467c5bcdb45a41d2a49fbb9ffca73d1380e99b
	Issue introduced in 6.4 with commit 10659034c622738bc1bfab8a76fc576c52d5acce and fixed in 6.12.28 with commit c649b9653ed09196e91d3f4b16b679041b3c42e6
	Issue introduced in 6.4 with commit 10659034c622738bc1bfab8a76fc576c52d5acce and fixed in 6.14.6 with commit 26dc701021302f11c8350108321d11763bd81dfe
	Issue introduced in 6.4 with commit 10659034c622738bc1bfab8a76fc576c52d5acce and fixed in 6.15-rc5 with commit dfd76010f8e821b66116dec3c7d90dd2403d1396

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-37916
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/net/ethernet/amd/pds_core/auxbus.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/9b467c5bcdb45a41d2a49fbb9ffca73d1380e99b
	https://git.kernel.org/stable/c/c649b9653ed09196e91d3f4b16b679041b3c42e6
	https://git.kernel.org/stable/c/26dc701021302f11c8350108321d11763bd81dfe
	https://git.kernel.org/stable/c/dfd76010f8e821b66116dec3c7d90dd2403d1396