| 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-37962: ksmbd: fix memory leak in parse_lease_state() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| ksmbd: fix memory leak in parse_lease_state() |
| |
| The previous patch that added bounds check for create lease context |
| introduced a memory leak. When the bounds check fails, the function |
| returns NULL without freeing the previously allocated lease_ctx_info |
| structure. |
| |
| This patch fixes the issue by adding kfree(lreq) before returning NULL |
| in both boundary check cases. |
| |
| The Linux kernel CVE team has assigned CVE-2025-37962 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.1.134 with commit 629dd37acc336ad778979361c351e782053ea284 and fixed in 6.1.139 with commit facf22c1a394c1e023dab5daf9a494f722771e1c |
| Issue introduced in 6.6.87 with commit 60b7207893a8a06c78441934931a08fdad63f18e and fixed in 6.6.91 with commit af9e2d4732a548db8f6f5a90c2c20a789a3d7240 |
| Issue introduced in 6.12.23 with commit 800c482c9ef5910f05e3a713943c67cc6c1d4939 and fixed in 6.12.29 with commit 2148d34371b06dac696c0497a98a6bf905a51650 |
| Issue introduced in 6.14.2 with commit 9a1b6ea955e6c7b29939a6d98701202f9d9644ec and fixed in 6.14.7 with commit 829e19ef741d9e9932abdc3bee5466195e0852cf |
| Issue introduced in 6.13.11 with commit a41cd52f00907a040ca22c73d4805bb79b0d0972 |
| |
| 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-37962 |
| 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 |
| |
| |
| 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/facf22c1a394c1e023dab5daf9a494f722771e1c |
| https://git.kernel.org/stable/c/af9e2d4732a548db8f6f5a90c2c20a789a3d7240 |
| https://git.kernel.org/stable/c/2148d34371b06dac696c0497a98a6bf905a51650 |
| https://git.kernel.org/stable/c/829e19ef741d9e9932abdc3bee5466195e0852cf |
| https://git.kernel.org/stable/c/eb4447bcce915b43b691123118893fca4f372a8f |
