CVE-2024-50186

See a problem?
Please try reporting it to the source first.
Source
https://cve.org/CVERecord?id=CVE-2024-50186
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2024-50186.json
JSON Data
https://api.test.osv.dev/v1/vulns/CVE-2024-50186
Downstream
Related
Published
2024-11-08T05:38:27.272Z
Modified
2026-03-11T07:52:55.075398Z
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 skcommonrelease in their error paths.

For example, we can use the same reproducer as in the above commit, but changing ping to arping. arping uses AFPACKET socket and if packetcreate 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 _sockcreate. 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 
{
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/50xxx/CVE-2024-50186.json",
    "cna_assigner": "Linux"
}
References

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
Introduced
78e4aa528a7b1204219d808310524344f627d069
Fixed
daf462ff3cde6ecf22b98d9ae770232c10d28de2
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
893eeba94c40d513cd0fe6539330ebdaea208c0e
Fixed
b7d22a79ff4e962b8af5ffe623abd1d6c179eb9f
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
454c454ed645fed051216b79622f7cb69c1638f5
Fixed
563e6892e21d6ecabdf62103fc4e7b326d212334
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
6cd4a78d962bebbaf8beb7d2ead3f34120e3f7b2
Fixed
8e1b72fd74bf9da3b099d09857f4e7f114f38e12
Fixed
631083143315d1b192bd7d915b967b37819e88ea
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
0 Unknown introduced commit / All previous commits are affected
Last affected
5dfe2408fd7dc4d2e7ac38a116ff0a37b1cfd3b9

Database specific

source 
"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2024-50186.json"