smb: client: fix use-after-free of signing key
Affects Linux kernel 3.12.0 through 6.6.69 and 6.7.0 through 6.12.1 on SMB2.1 mounts using signing (sign mount option). Fixed in 6.6.70 and 6.12.2.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 6.6.70, 6.12.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
The Linux kernel's SMB client (CIFS/SMB networking filesystem) is affected, specifically SMB2.1 mounts using packet signing. A race condition can cause the client to use a signing key after it has already been freed, which could lead to a crash or memory corruption.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original 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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
3.12
- KernelLinux
From 3.12.0 · fixed in 6.6.70; From 6.7.0 · fixed in 6.12.2
References 4
Questions about CVE-2024-53179
What does this mean?
The Linux kernel SMB client can use the session signing key after it has been freed, a use-after-free bug. The key is the one stored in the session's auth key response.Source: git.kernel.org
Am I affected, and how do I check?
Kernels from 3.12.0 up to 6.6.70 and from 6.7.0 up to 6.12.2 are listed as affected, but only on SMB2.1 mounts with signing enabled (the sign mount option). To check a setup, run uname -r for the kernel version and review the options of any SMB mounts.Source: git.kernel.org
What should I do about it?
Update the kernel to 6.6.70 or later on the 6.6 branch, or to 6.12.2 or later on the 6.12 branch.Source: git.kernel.org
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data