linux-cve-announce - CVE-2025-39783: PCI: endpoint: Fix configfs group list head handling

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: <2025091150-CVE-2025-39783-b911@gregkh>
Date: Thu, 11 Sep 2025 18:57:01 +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-39783: PCI: endpoint: Fix configfs group list head handling

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

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

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

PCI: endpoint: Fix configfs group list head handling

Doing a list_del() on the epf_group field of struct pci_epf_driver in
pci_epf_remove_cfs() is not correct as this field is a list head, not
a list entry. This list_del() call triggers a KASAN warning when an
endpoint function driver which has a configfs attribute group is torn
down:

==================================================================
BUG: KASAN: slab-use-after-free in pci_epf_remove_cfs+0x17c/0x198
Write of size 8 at addr ffff00010f4a0d80 by task rmmod/319

CPU: 3 UID: 0 PID: 319 Comm: rmmod Not tainted 6.16.0-rc2 #1 NONE
Hardware name: Radxa ROCK 5B (DT)
Call trace:
show_stack+0x2c/0x84 (C)
dump_stack_lvl+0x70/0x98
print_report+0x17c/0x538
kasan_report+0xb8/0x190
__asan_report_store8_noabort+0x20/0x2c
pci_epf_remove_cfs+0x17c/0x198
pci_epf_unregister_driver+0x18/0x30
nvmet_pci_epf_cleanup_module+0x24/0x30 [nvmet_pci_epf]
__arm64_sys_delete_module+0x264/0x424
invoke_syscall+0x70/0x260
el0_svc_common.constprop.0+0xac/0x230
do_el0_svc+0x40/0x58
el0_svc+0x48/0xdc
el0t_64_sync_handler+0x10c/0x138
el0t_64_sync+0x198/0x19c
...

Remove this incorrect list_del() call from pci_epf_remove_cfs().

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


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

	Issue introduced in 4.18 with commit ef1433f717a2c63747a519d86965d73ff9bd08b3 and fixed in 5.4.297 with commit 80ea6e6904fb2ba4ccb5d909579988466ec65358
	Issue introduced in 4.18 with commit ef1433f717a2c63747a519d86965d73ff9bd08b3 and fixed in 5.10.241 with commit d5aecddc3452371d9da82cdbb0c715812524b54b
	Issue introduced in 4.18 with commit ef1433f717a2c63747a519d86965d73ff9bd08b3 and fixed in 5.15.190 with commit dc4ffbd571716ff3b171418fb03abe80e720a7b1
	Issue introduced in 4.18 with commit ef1433f717a2c63747a519d86965d73ff9bd08b3 and fixed in 6.1.149 with commit 409af8b9f7b4f23cd0464e71c6cd6fe13c076ae2
	Issue introduced in 4.18 with commit ef1433f717a2c63747a519d86965d73ff9bd08b3 and fixed in 6.6.103 with commit 0758862386f114d9ab1e23181461bd1e2e9ec4c6
	Issue introduced in 4.18 with commit ef1433f717a2c63747a519d86965d73ff9bd08b3 and fixed in 6.12.44 with commit 6cf65505523224cab1449d726d2ce8180c2941ee
	Issue introduced in 4.18 with commit ef1433f717a2c63747a519d86965d73ff9bd08b3 and fixed in 6.16.4 with commit a302bd89db35d8b7e279de4d2b41c16c7f191069
	Issue introduced in 4.18 with commit ef1433f717a2c63747a519d86965d73ff9bd08b3 and fixed in 6.17-rc1 with commit d79123d79a8154b4318529b7b2ff7e15806f480b

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-39783
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/pci/endpoint/pci-epf-core.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/80ea6e6904fb2ba4ccb5d909579988466ec65358
	https://git.kernel.org/stable/c/d5aecddc3452371d9da82cdbb0c715812524b54b
	https://git.kernel.org/stable/c/dc4ffbd571716ff3b171418fb03abe80e720a7b1
	https://git.kernel.org/stable/c/409af8b9f7b4f23cd0464e71c6cd6fe13c076ae2
	https://git.kernel.org/stable/c/0758862386f114d9ab1e23181461bd1e2e9ec4c6
	https://git.kernel.org/stable/c/6cf65505523224cab1449d726d2ce8180c2941ee
	https://git.kernel.org/stable/c/a302bd89db35d8b7e279de4d2b41c16c7f191069
	https://git.kernel.org/stable/c/d79123d79a8154b4318529b7b2ff7e15806f480b