CVE-2024-50186net: explicitly clear the sk pointer, when pf->create fails
- 7.8HighCVSS base score
- 0.23%Exploitation in 30 daysEPSS · top 86% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 18 days later
· 18 days later
Published
- 21 months later
· 21 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| CISA-ADPADP (enrichment) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.23% · top 86% of all CVEs (15 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 78e4aa528a7b1204219d808310524344f627d069 – < daf462ff3cde6ecf22b98d9ae770232c10d28de2
- affected 893eeba94c40d513cd0fe6539330ebdaea208c0e – < b7d22a79ff4e962b8af5ffe623abd1d6c179eb9f
- affected 454c454ed645fed051216b79622f7cb69c1638f5 – < 563e6892e21d6ecabdf62103fc4e7b326d212334
- affected 6cd4a78d962bebbaf8beb7d2ead3f34120e3f7b2 – < 8e1b72fd74bf9da3b099d09857f4e7f114f38e12
- affected 6cd4a78d962bebbaf8beb7d2ead3f34120e3f7b2 – < 631083143315d1b192bd7d915b967b37819e88ea
- affected 5dfe2408fd7dc4d2e7ac38a116ff0a37b1cfd3b9
- affected 5.15.162 – < 5.15.168
- affected 6.1.96 – < 6.1.113
- affected 6.6.36 – < 6.6.57
- affected 6.9.7 – < 6.10
- affected 6.10
- unaffected < 6.10
- unaffected 5.15.168 – ≤ 5.15.*
- unaffected 6.1.113 – ≤ 6.1.*
- unaffected 6.6.57 – ≤ 6.6.*
- unaffected 6.11.4 – ≤ 6.11.*
- unaffected 6.12 – ≤ *
References
References6
- https://git.kernel.org/stable/c/daf462ff3cde6ecf22b98d9ae770232c10d28de2 (opens in a new tab)
- https://git.kernel.org/stable/c/b7d22a79ff4e962b8af5ffe623abd1d6c179eb9f (opens in a new tab)
- https://git.kernel.org/stable/c/563e6892e21d6ecabdf62103fc4e7b326d212334 (opens in a new tab)
- https://git.kernel.org/stable/c/8e1b72fd74bf9da3b099d09857f4e7f114f38e12 (opens in a new tab)
- https://git.kernel.org/stable/c/631083143315d1b192bd7d915b967b37819e88ea (opens in a new tab)
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-44688 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-50186)Record last updated .