linux-cve-announce - CVE-2025-39832: net/mlx5: Fix lockdep assertion on sync reset unload event

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: <2025091657-CVE-2025-39832-6bbc@gregkh>
Date: Tue, 16 Sep 2025 15:09:00 +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-39832: net/mlx5: Fix lockdep assertion on sync reset unload event

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

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

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

net/mlx5: Fix lockdep assertion on sync reset unload event

Fix lockdep assertion triggered during sync reset unload event. When the
sync reset flow is initiated using the devlink reload fw_activate
option, the PF already holds the devlink lock while handling unload
event. In this case, delegate sync reset unload event handling back to
the devlink callback process to avoid double-locking and resolve the
lockdep warning.

Kernel log:
WARNING: CPU: 9 PID: 1578 at devl_assert_locked+0x31/0x40
[...]
Call Trace:
<TASK>
 mlx5_unload_one_devl_locked+0x2c/0xc0 [mlx5_core]
 mlx5_sync_reset_unload_event+0xaf/0x2f0 [mlx5_core]
 process_one_work+0x222/0x640
 worker_thread+0x199/0x350
 kthread+0x10b/0x230
 ? __pfx_worker_thread+0x10/0x10
 ? __pfx_kthread+0x10/0x10
 ret_from_fork+0x8e/0x100
 ? __pfx_kthread+0x10/0x10
 ret_from_fork_asm+0x1a/0x30
</TASK>

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

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

	Issue introduced in 6.5 with commit 7a9770f1bfeaeddf5afabd3244e2c4c4966be37d and fixed in 6.6.104 with commit ddac9d0fe2493dd550cbfc75eeaf31e9b6dac959
	Issue introduced in 6.5 with commit 7a9770f1bfeaeddf5afabd3244e2c4c4966be37d and fixed in 6.12.45 with commit 0c87dba9ccd3801d3b503f0b4fd41be343af4f06
	Issue introduced in 6.5 with commit 7a9770f1bfeaeddf5afabd3244e2c4c4966be37d and fixed in 6.16.5 with commit 06d897148e79638651800d851a69547b56b4be2e
	Issue introduced in 6.5 with commit 7a9770f1bfeaeddf5afabd3244e2c4c4966be37d and fixed in 6.17-rc4 with commit 902a8bc23a24882200f57cadc270e15a2cfaf2bb

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-39832
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/mellanox/mlx5/core/devlink.c
	drivers/net/ethernet/mellanox/mlx5/core/fw_reset.c
	drivers/net/ethernet/mellanox/mlx5/core/fw_reset.h

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/ddac9d0fe2493dd550cbfc75eeaf31e9b6dac959
	https://git.kernel.org/stable/c/0c87dba9ccd3801d3b503f0b4fd41be343af4f06
	https://git.kernel.org/stable/c/06d897148e79638651800d851a69547b56b4be2e
	https://git.kernel.org/stable/c/902a8bc23a24882200f57cadc270e15a2cfaf2bb