CVE-2024-50186
- Source
- https://cve.org/CVERecord?id=CVE-2024-50186
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-50186.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2024-50186
- Downstream
BELL (1)
CLSA (1)
DEBIAN (1)
OESA (1)
openSUSE (2)
RHSA (1)
SUSE (11)
- Related
- Published
- 2024-11-08T05:38:27Z
- Modified
- 2026-10-20T10:31:19Z
- Severity
-
- 7.8 (High) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
- Summary
- net: explicitly clear the sk pointer, when pf->create fails
- Details
-
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.
- Database specific
{ "cna_assigner": "Linux", "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/50xxx/CVE-2024-50186.json" }- References
-
- https://git.kernel.org/stable/c/563e6892e21d6ecabdf62103fc4e7b326d212334
- https://git.kernel.org/stable/c/631083143315d1b192bd7d915b967b37819e88ea
- https://git.kernel.org/stable/c/8e1b72fd74bf9da3b099d09857f4e7f114f38e12
- https://git.kernel.org/stable/c/b7d22a79ff4e962b8af5ffe623abd1d6c179eb9f
- https://git.kernel.org/stable/c/daf462ff3cde6ecf22b98d9ae770232c10d28de2
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/50xxx/CVE-2024-50186.json
- https://nvd.nist.gov/vuln/detail/CVE-2024-50186
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced78e4aa528a7b1204219d808310524344f627d069Fixeddaf462ff3cde6ecf22b98d9ae770232c10d28de2
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced893eeba94c40d513cd0fe6539330ebdaea208c0eFixedb7d22a79ff4e962b8af5ffe623abd1d6c179eb9f
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced454c454ed645fed051216b79622f7cb69c1638f5Fixed563e6892e21d6ecabdf62103fc4e7b326d212334
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced6cd4a78d962bebbaf8beb7d2ead3f34120e3f7b2Fixed8e1b72fd74bf9da3b099d09857f4e7f114f38e12Fixed631083143315d1b192bd7d915b967b37819e88ea
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced5.15.162Fixed5.15.168
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced6.1.96Fixed6.1.113
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced6.6.36Fixed6.6.57
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced6.9.7Fixed6.10
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced5dfe2408fd7dc4d2e7ac38a116ff0a37b1cfd3b9
Affected versions
v5.*
v6.*
Linux / Kernel
Package
- Name
- Kernel