| From bippy-1.2.0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@kernel.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2025-37954: smb: client: Avoid race in open_cached_dir with lease breaks |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| smb: client: Avoid race in open_cached_dir with lease breaks |
| |
| A pre-existing valid cfid returned from find_or_create_cached_dir might |
| race with a lease break, meaning open_cached_dir doesn't consider it |
| valid, and thinks it's newly-constructed. This leaks a dentry reference |
| if the allocation occurs before the queued lease break work runs. |
| |
| Avoid the race by extending holding the cfid_list_lock across |
| find_or_create_cached_dir and when the result is checked. |
| |
| The Linux kernel CVE team has assigned CVE-2025-37954 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 6.6.91 with commit 2ed98e89ebc2e1bc73534dc3c18cb7843a889ff9 |
| Fixed in 6.12.29 with commit 571dcf3d27b24800c171aea7b5e04ff06d10e2e9 |
| Fixed in 6.14.7 with commit 2407265dc32bc8cc45b62a612c2a214ba9038e8b |
| Fixed in 6.15 with commit 3ca02e63edccb78ef3659bebc68579c7224a6ca2 |
| |
| 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-37954 |
| 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/cached_dir.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/2ed98e89ebc2e1bc73534dc3c18cb7843a889ff9 |
| https://git.kernel.org/stable/c/571dcf3d27b24800c171aea7b5e04ff06d10e2e9 |
| https://git.kernel.org/stable/c/2407265dc32bc8cc45b62a612c2a214ba9038e8b |
| https://git.kernel.org/stable/c/3ca02e63edccb78ef3659bebc68579c7224a6ca2 |
