CVE-2024-50186

HIGH EPSS 13.8%
Published Nov 8, 20241y ago · Modified Jun 17, 20262w ago
7.8 CVSS 3.1
High
Find Similar
Published Nov 8, 2024 1y ago
Last Modified Jun 17, 2026 2w ago

Description

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.

CVSS Details

Base Score
7.8
Exploitability
1.8
Impact
5.9
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Attack Vector Local
Attack Complexity Low
Privileges Required Low
User Interaction None
Scope Unchanged
Confidentiality High
Integrity High
Availability High

Threat Intelligence

EPSS Exploit Probability
13.8% percentile
Exploit & Patch Status
No Known Exploit
Patch Available

Weaknesses 1

CWE-416 Use After Free Memory Safety

Affected Products 7

VendorProductVersionRange
linuxlinux_kernel*≥5.15.162  –  <5.15.168
linuxlinux_kernel*≥6.1.96  –  <6.1.113
linuxlinux_kernel*≥6.6.36  –  <6.6.57
linuxlinux_kernel*≥6.9.7  –  <6.10
linuxlinux_kernel*≥6.10  –  <6.11.4
linuxlinux_kernel6.12any
linuxlinux_kernel6.12any

References 6

  • git.kernel.org https://git.kernel.org/stable/c/563e6892e21d6ecabdf62103fc4e7b326d212334
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/631083143315d1b192bd7d915b967b37819e88ea
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/8e1b72fd74bf9da3b099d09857f4e7f114f38e12
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/b7d22a79ff4e962b8af5ffe623abd1d6c179eb9f
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/daf462ff3cde6ecf22b98d9ae770232c10d28de2
    Patch
  • lists.debian.org https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html

Remediation

  • git.kernel.org https://git.kernel.org/stable/c/563e6892e21d6ecabdf62103fc4e7b326d212334
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/631083143315d1b192bd7d915b967b37819e88ea
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/8e1b72fd74bf9da3b099d09857f4e7f114f38e12
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/b7d22a79ff4e962b8af5ffe623abd1d6c179eb9f
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/daf462ff3cde6ecf22b98d9ae770232c10d28de2
    Patch