From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A77F93ED11F for ; Fri, 8 May 2026 14:26:57 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778250417; cv=none; b=K/84qfCBjdE1oaeRmQoiNSPHR+kw/9D0ovbtjwKtqBvRCYxdiRW8m0iKhUY3KyRmaB9ENhUhRzGEB3Gx7w8Or8uwD6RJi/y6Z7RfybJkXcZOV9SyL/jAOXnmsTuHmVlgXSYdL6/VQY2AjPXpGvZv0x+kkkhoJvk+X/eqsi4YkXU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778250417; c=relaxed/simple; bh=GBKWrxsOzrrA1SrcwThQTPC2OZhFtqAZTDIvWoTuOJc=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=ttTGIEjtvbe4V96ZE5i1l3t++P94GNa6B2ENLQyV9ZhE/228oIZ4IeNaE4k3H0QaDqHkzSNBg52vFNvnExz8UtKUlIgAAsdzgrJUCfcx4JhB7Oxe1G6q056iLj7nADbOeyXUaZivFbEVS1UHB92xkhqab2XsIm5FYCUJmeNZD3o= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=nADFOo3q; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="nADFOo3q" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 06754C2BCB0; Fri, 8 May 2026 14:26:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1778250417; bh=GBKWrxsOzrrA1SrcwThQTPC2OZhFtqAZTDIvWoTuOJc=; h=From:To:Cc:Subject:Date:Reply-To:From; b=nADFOo3q7xUUnl0pWlOrSHlLZwznkO/cB+XOsDfaVMYv4A+6hiDRQ3BdKX4R3FRAj OoNEDpEX0btVETmSUSFBo/6IqXpwT/RbPOykAwHUMIJS35IJAkhwy2quyDP4rlfpjE /EfVVL3bNLhpUXaLlUrn4CFjOYrCJO+2h3F4xX8k= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-43468: net/mlx5: Fix deadlock between devlink lock and esw->wq Date: Fri, 8 May 2026 16:23:17 +0200 Message-ID: <2026050803-CVE-2026-43468-8a20@gregkh> X-Mailer: git-send-email 2.54.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=4282; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=Xp/zYSVMO0GF0EaQ8Yity1XDE/VmBr/eUit0GrpkiNw=; b=owGbwMvMwCRo6H6F97bub03G02pJDJl/P/YET1w4e979BQw7AsWUN+7I+Lf1xeO5TlO1uh4Fv 9/u5unA1xHLwiDIxCArpsjyZRvP0f0VhxS9DG1Pw8xhZQIZwsDFKQATuZHFsGApN29bxUQts5Bb Dgs/uczseJM67w3DXPEcDcGN97LljqezGZofXH1fxi9zEQA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Fix deadlock between devlink lock and esw->wq esw->work_queue executes esw_functions_changed_event_handler -> esw_vfs_changed_event_handler and acquires the devlink lock. .eswitch_mode_set (acquires devlink lock in devlink_nl_pre_doit) -> mlx5_devlink_eswitch_mode_set -> mlx5_eswitch_disable_locked -> mlx5_eswitch_event_handler_unregister -> flush_workqueue deadlocks when esw_vfs_changed_event_handler executes. Fix that by no longer flushing the work to avoid the deadlock, and using a generation counter to keep track of work relevance. This avoids an old handler manipulating an esw that has undergone one or more mode changes: - the counter is incremented in mlx5_eswitch_event_handler_unregister. - the counter is read and passed to the ephemeral mlx5_host_work struct. - the work handler takes the devlink lock and bails out if the current generation is different than the one it was scheduled to operate on. - mlx5_eswitch_cleanup does the final draining before destroying the wq. No longer flushing the workqueue has the side effect of maybe no longer cancelling pending vport_change_handler work items, but that's ok since those are disabled elsewhere: - mlx5_eswitch_disable_locked disables the vport eq notifier. - mlx5_esw_vport_disable disarms the HW EQ notification and marks vport->enabled under state_lock to false to prevent pending vport handler from doing anything. - mlx5_eswitch_cleanup destroys the workqueue and makes sure all events are disabled/finished. The Linux kernel CVE team has assigned CVE-2026-43468 to this issue. Affected and fixed versions =========================== Issue introduced in 6.0 with commit f1bc646c9a06f09aad5d8bacb87103b5573ee45e and fixed in 6.1.167 with commit 0de867f6e34eae6907b367fd152c55e61cb98608 Issue introduced in 6.0 with commit f1bc646c9a06f09aad5d8bacb87103b5573ee45e and fixed in 6.6.130 with commit 957d2a58f7f8ebcbdd0a85935e0d2675134b890d Issue introduced in 6.0 with commit f1bc646c9a06f09aad5d8bacb87103b5573ee45e and fixed in 6.12.78 with commit 3c7313cb41b1b427078440364d2f042c276a1c0b Issue introduced in 6.0 with commit f1bc646c9a06f09aad5d8bacb87103b5573ee45e and fixed in 6.18.19 with commit 4a7838bebc38374f74baaf88bf2cf8d439a92923 Issue introduced in 6.0 with commit f1bc646c9a06f09aad5d8bacb87103b5573ee45e and fixed in 6.19.9 with commit 90e7e5d14d0bd25ffd019a3aa39d9f1c05fedbe1 Issue introduced in 6.0 with commit f1bc646c9a06f09aad5d8bacb87103b5573ee45e and fixed in 7.0 with commit aed763abf0e905b4b8d747d1ba9e172961572f57 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-2026-43468 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/eswitch.c drivers/net/ethernet/mellanox/mlx5/core/eswitch.h drivers/net/ethernet/mellanox/mlx5/core/eswitch_offloads.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/0de867f6e34eae6907b367fd152c55e61cb98608 https://git.kernel.org/stable/c/957d2a58f7f8ebcbdd0a85935e0d2675134b890d https://git.kernel.org/stable/c/3c7313cb41b1b427078440364d2f042c276a1c0b https://git.kernel.org/stable/c/4a7838bebc38374f74baaf88bf2cf8d439a92923 https://git.kernel.org/stable/c/90e7e5d14d0bd25ffd019a3aa39d9f1c05fedbe1 https://git.kernel.org/stable/c/aed763abf0e905b4b8d747d1ba9e172961572f57