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]
Date: Thu, 29 Feb 2024 06:43:23 +0100
From: Greg Kroah-Hartman <>
Subject: CVE-2023-52480: ksmbd: fix race condition between session lookup and expire



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

ksmbd: fix race condition between session lookup and expire

 Thread A                        +  Thread B
 ksmbd_session_lookup            |  smb2_sess_setup
   sess = xa_load                |
                                 |    xa_erase(&conn->sessions, sess->id);
                                 |    ksmbd_session_destroy(sess) --> kfree(sess)
   // UAF!                       |
   sess->last_active = jiffies   |

This patch add rwsem to fix race condition between ksmbd_session_lookup
and ksmbd_expire_session.

The Linux kernel CVE team has assigned CVE-2023-52480 to this issue.

Affected and fixed versions

	Fixed in 5.15.145 with commit c77fd3e25a51
	Fixed in 6.1.57 with commit a2ca5fd3dbcc
	Fixed in 6.5.7 with commit 18ced78b0ebc
	Fixed in 6.6 with commit 53ff5cf89142

Please see or 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
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:


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:

Powered by blists - more mailing lists