| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2024-53179: smb: client: fix use-after-free of signing key |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| smb: client: fix use-after-free of signing key |
| |
| Customers have reported use-after-free in @ses->auth_key.response with |
| SMB2.1 + sign mounts which occurs due to following race: |
| |
| task A task B |
| cifs_mount() |
| dfs_mount_share() |
| get_session() |
| cifs_mount_get_session() cifs_send_recv() |
| cifs_get_smb_ses() compound_send_recv() |
| cifs_setup_session() smb2_setup_request() |
| kfree_sensitive() smb2_calc_signature() |
| crypto_shash_setkey() *UAF* |
| |
| Fix this by ensuring that we have a valid @ses->auth_key.response by |
| checking whether @ses->ses_status is SES_GOOD or SES_EXITING with |
| @ses->ses_lock held. After commit 24a9799aa8ef ("smb: client: fix UAF |
| in smb2_reconnect_server()"), we made sure to call ->logoff() only |
| when @ses was known to be good (e.g. valid ->auth_key.response), so |
| it's safe to access signing key when @ses->ses_status == SES_EXITING. |
| |
| The Linux kernel CVE team has assigned CVE-2024-53179 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 6.6.70 with commit 39619c65ab4bbb3e78c818f537687653e112764d |
| Fixed in 6.12.2 with commit 0e2b654a3848bf9da3b0d54c1ccf3f1b8c635591 |
| Fixed in 6.13 with commit 343d7fe6df9e247671440a932b6a73af4fa86d95 |
| |
| 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-53179 |
| 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/smb2proto.h |
| 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/39619c65ab4bbb3e78c818f537687653e112764d |
| https://git.kernel.org/stable/c/0e2b654a3848bf9da3b0d54c1ccf3f1b8c635591 |
| https://git.kernel.org/stable/c/343d7fe6df9e247671440a932b6a73af4fa86d95 |
