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
| ||
|
Message-ID: <2025050115-CVE-2025-37776-9bfb@gregkh> Date: Thu, 1 May 2025 15:07:24 +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-37776: ksmbd: fix use-after-free in smb_break_all_levII_oplock() From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in smb_break_all_levII_oplock() There is a room in smb_break_all_levII_oplock that can cause racy issues when unlocking in the middle of the loop. This patch use read lock to protect whole loop. The Linux kernel CVE team has assigned CVE-2025-37776 to this issue. Affected and fixed versions =========================== Fixed in 6.6.88 with commit 296cb5457cc6f4a754c4ae29855f8a253d52bcc6 Fixed in 6.12.25 with commit d54ab1520d43e95f9b2e22d7a05fc9614192e5a5 Fixed in 6.14.4 with commit d73686367ad68534257cd88a36ca3c52cb8b81d8 Fixed in 6.15-rc3 with commit 18b4fac5ef17f77fed9417d22210ceafd6525fc7 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-37776 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/server/oplock.c fs/smb/server/oplock.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/296cb5457cc6f4a754c4ae29855f8a253d52bcc6 https://git.kernel.org/stable/c/d54ab1520d43e95f9b2e22d7a05fc9614192e5a5 https://git.kernel.org/stable/c/d73686367ad68534257cd88a36ca3c52cb8b81d8 https://git.kernel.org/stable/c/18b4fac5ef17f77fed9417d22210ceafd6525fc7
Powered by blists - more mailing lists