CVE-2024-50086: ksmbd: fix user-after-free from session log off
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix user-after-free from session log off
There is racy issue between smb2 session log off and smb2 session setup. It will cause user-after-free from session log off. This add sessionlock when setting SMB2SESSIONEXPIRED and referece count to session struct not to free session while it is being used.
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 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1 - Upgrade
Upgrade
debian/linux-6.1to a version that resolves this vulnerability.Fixed in 6.1.129-1~deb11u1
Event History
Frequently Asked Questions
What is the severity of CVE-2024-50086?
The CVE-2024-50086 has a moderate severity level due to the user-after-free vulnerability in the Linux kernel.
How do I fix CVE-2024-50086?
You can mitigate CVE-2024-50086 by updating the Linux kernel to a version that includes the fix, as detailed in the security advisories.
Which versions of the Linux kernel are affected by CVE-2024-50086?
CVE-2024-50086 affects Linux kernel versions from 6.2 up to, but not including, 6.6.58, as well as some release candidates.
What types of issues does CVE-2024-50086 cause?
CVE-2024-50086 can lead to potential memory corruption due to a race condition during the SMB2 session log off and setup.
Is CVE-2024-50086 a remote exploitation risk?
Yes, CVE-2024-50086 can be exploited remotely under certain conditions, making it important to address promptly.