CVE-2024-53179: Linux kernel · smb: client: fix use-after-free of signing key
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 9.8 Critical · fixed in 6.8.0-1029.31~22.04.1 : patch Linux kernel as a priority.
Data as of 28 Oct 2026, 11:13 UTC
- Patch
- Available – fixed in 6.8.0-1029.31~22.04.1, 6.8.0-1029.34~22.04.1, 6.8.0-1030.32~22.04.1 +31
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-7379-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7380-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7381-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7382-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7379-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7513-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7513-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7514-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7515-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7513-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7522-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7515-2 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-nvidiapkg:deb/ubuntu/linux-azure-nvidia?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- ubuntu.com/security/CVE-2024-53179 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-53179 (opens in a new tab)
- git.kernel.org/linus/343d7fe6df9e247671440a932b6a73af4fa86d95 (opens in a new tab)
- git.kernel.org/stable/c/0e2b654a3848bf9da3b0d54c1ccf3f1b8c635591 (opens in a new tab)
- git.kernel.org/stable/c/343d7fe6df9e247671440a932b6a73af4fa86d95 (opens in a new tab)
- ubuntu.com/security/notices/USN-7379-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7380-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7381-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7382-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7379-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7513-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7513-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7514-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7515-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7513-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7522-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7515-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7523-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7524-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7513-4 (opens in a new tab)