CVE-2024-53179: smb: client: fix use-after-free of signing key
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->authkey.response with SMB2.1 + sign mounts which occurs due to following race:
task A task B cifsmount() dfsmountshare() getsession() cifsmountgetsession() cifssendrecv() cifsgetsmbses() compoundsendrecv() cifssetupsession() smb2setuprequest() kfreesensitive() smb2calcsignature() cryptoshashsetkey() UAF
Fix this by ensuring that we have a valid @ses->authkey.response by checking whether @ses->sesstatus is SESGOOD or SESEXITING with @ses->seslock held. After commit 24a9799aa8ef ("smb: client: fix UAF in smb2reconnectserver()"), we made sure to call ->logoff() only when @ses was known to be good (e.g. valid ->authkey.response), so it's safe to access signing key when @ses->sesstatus == SESEXITING.
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.27-1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch 24a9799aa8ef - Configuration
In the SMB2 client code path, prevent UAF of @ses->auth_key.response by ensuring a valid signing key: guard access to @ses->auth_key.response by checking whether @ses->ses_status is SES_GOOD or SES_EXITING while holding @ses->ses_lock; this corresponds to the fix described as 'smb: client: fix use-after-free of signing key' in smb2_reconnect_server().
Linux kernel SMB client (cifs/smb2) Session signing key use-after-free fix = Check @ses->ses_status is SES_GOOD or SES_EXITING with @ses->ses_lock held before accessing @ses->auth_key.response (signing key)
Event History
Frequently Asked Questions
What is the severity of CVE-2024-53179?
CVE-2024-53179 has been reported as a medium-severity vulnerability affecting the Linux kernel.
How do I fix CVE-2024-53179?
To remediate CVE-2024-53179, update your Linux kernel to version 6.12.19-1, 6.12.20-1, or any version above 6.7 and less than 6.6.70.
What platforms are impacted by CVE-2024-53179?
CVE-2024-53179 affects the Linux kernel running versions between 5.10.223-1 and up to but not including 6.6.70.
What types of attacks can CVE-2024-53179 facilitate?
CVE-2024-53179 can potentially allow unauthorized access or manipulation of SMB2.1 traffic due to a use-after-free vulnerability.
Is there a recommended action for users of Debian concerning CVE-2024-53179?
Users of Debian should upgrade to the latest kernel versions provided, specifically versions 6.12.19-1 or 6.12.20-1, to mitigate CVE-2024-53179.