high
7.8
CWE
416
Advisory Published
Updated

CVE-2024-50186: net: explicitly clear the sk pointer, when pf->create fails

First published: Fri Nov 08 2024(Updated: )

In the Linux kernel, the following vulnerability has been resolved: net: explicitly clear the sk pointer, when pf->create fails We have recently noticed the exact same KASAN splat as in commit 6cd4a78d962b ("net: do not leave a dangling sk pointer, when socket creation fails"). The problem is that commit did not fully address the problem, as some pf->create implementations do not use sk_common_release in their error paths. For example, we can use the same reproducer as in the above commit, but changing ping to arping. arping uses AF_PACKET socket and if packet_create fails, it will just sk_free the allocated sk object. While we could chase all the pf->create implementations and make sure they NULL the freed sk object on error from the socket, we can't guarantee future protocols will not make the same mistake. So it is easier to just explicitly NULL the sk pointer upon return from pf->create in __sock_create. We do know that pf->create always releases the allocated sk object on error, so if the pointer is not NULL, it is definitely dangling.

Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Affected SoftwareAffected VersionHow to fix
Linux Kernel>=5.15.162<5.15.168
Linux Kernel>=6.1.96<6.1.113
Linux Kernel>=6.6.36<6.6.57
Linux Kernel>=6.9.7<6.10
Linux Kernel>=6.10<6.11.4
Linux Kernel=6.12-rc1
Linux Kernel=6.12-rc2
debian/linux
5.10.223-1
5.10.226-1
6.1.123-1
6.1.128-1
6.12.12-1
6.12.15-1
debian/linux-6.1
6.1.119-1~deb11u1

Remedy

https://git.kernel.org/stable/c/563e6892e21d6ecabdf62103fc4e7b326d212334

Remedy

https://git.kernel.org/stable/c/631083143315d1b192bd7d915b967b37819e88ea

Remedy

https://git.kernel.org/stable/c/8e1b72fd74bf9da3b099d09857f4e7f114f38e12

Remedy

https://git.kernel.org/stable/c/b7d22a79ff4e962b8af5ffe623abd1d6c179eb9f

Remedy

https://git.kernel.org/stable/c/daf462ff3cde6ecf22b98d9ae770232c10d28de2

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2024-50186?

    CVE-2024-50186 has a medium severity rating due to its impact on potential security risks in the Linux kernel.

  • How do I fix CVE-2024-50186?

    To fix CVE-2024-50186, you should upgrade to the patched versions such as linux 5.10.223-1, 5.10.226-1, or any subsequent versions mentioned in the vulnerability details.

  • Which versions of the Linux kernel are affected by CVE-2024-50186?

    CVE-2024-50186 affects multiple versions of the Linux kernel, particularly those before the specified remedial versions such as 5.10.223-1 and later.

  • What is the cause of CVE-2024-50186?

    CVE-2024-50186 is caused by a failure to explicitly clear the sk pointer in the Linux kernel during socket creation, leading to potential security vulnerabilities.

  • Can CVE-2024-50186 be exploited remotely?

    Yes, CVE-2024-50186 can potentially be exploited remotely, emphasizing the importance of applying recommended patches promptly.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203