CVE-2024-50260: sock_map: fix a NULL pointer dereference in sock_map_link_update_prog()
In the Linux kernel, the following vulnerability has been resolved:
sockmap: fix a NULL pointer dereference in sockmaplinkupdateprog()
The following race condition could trigger a NULL pointer dereference:
sockmaplinkdetach(): sockmaplinkupdateprog(): mutexlock(&sockmapmutex); ... sockmaplink->map = NULL; mutexunlock(&sockmapmutex); mutexlock(&sockmapmutex); ... sockmapproglinklookup(sockmaplink->map); mutexunlock(&sockmapmutex); <continue>
Fix it by adding a NULL pointer check. In this specific case, it makes no sense to update a link which is being released.
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
Event History
Frequently Asked Questions
What is the severity of CVE-2024-50260?
CVE-2024-50260 is classified as a vulnerability that can lead to a NULL pointer dereference in the Linux kernel.
How do I fix CVE-2024-50260?
To remediate CVE-2024-50260, update to the patched version of the Linux kernel that addresses the vulnerability.
Which versions of the Linux kernel are affected by CVE-2024-50260?
CVE-2024-50260 affects Linux kernel versions from 6.10 to 6.11.7 and specific release candidates from 6.12.
What components are implicated in CVE-2024-50260?
CVE-2024-50260 involves the sock_map component and its functions such as sock_map_link_update_prog().
Is there a known exploit for CVE-2024-50260?
As of now, there are no public exploits for CVE-2024-50260, but it is advisable to apply patches promptly.