linux-cve-announce - CVE-2024-39468: smb: client: fix deadlock in smb2_find_smb

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2024062500-CVE-2024-39468-11d2@gregkh>
Date: Tue, 25 Jun 2024 16:29:01 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-39468: smb: client: fix deadlock in smb2_find_smb_tcon()

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

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

smb: client: fix deadlock in smb2_find_smb_tcon()

Unlock cifs_tcp_ses_lock before calling cifs_put_smb_ses() to avoid such
deadlock.

The Linux kernel CVE team has assigned CVE-2024-39468 to this issue.


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

	Fixed in 6.1.94 with commit b09b556e4896
	Fixed in 6.6.34 with commit 225de871ddf9
	Fixed in 6.9.5 with commit 8d0f5f1ccf67
	Fixed in 6.10-rc3 with commit 02c418774f76

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-2024-39468
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:
	fs/smb/client/smb2transport.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/b09b556e48968317887a11243a5331a7bc00ece5
	https://git.kernel.org/stable/c/225de871ddf994f69a57f035709cad9c0ab8615a
	https://git.kernel.org/stable/c/8d0f5f1ccf675454a833a573c53830a49b7d1a47
	https://git.kernel.org/stable/c/02c418774f76a0a36a6195c9dbf8971eb4130a15