Answer in brief
CVE-2024-50186 records a Unknown severity vulnerability in net: explicitly clear the sk pointer, when pf->create fails. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=78e4aa528a7b1204219d808310524344f627d069 <daf462ff3cde6ecf22b98d9ae770232c10d28de2 || >=893eeba94c40d513cd0fe6539330ebdaea208c0e <b7d22a79ff4e962b8af5ffe623abd1d6c179eb9f || >=454c454ed645fed051216b79622f7cb69c1638f5 <563e6892e21d6ecabdf62103fc4e7b326d212334 || >=6cd4a78d962bebbaf8beb7d2ead3f34120e3f7b2 <8e1b72fd74bf9da3b099d09857f4e7f114f38e12 || >=6cd4a78d962bebbaf8beb7d2ead3f34120e3f7b2 <631083143315d1b192bd7d915b967b37819e88ea || 5dfe2408fd7dc4d2e7ac38a116ff0a37b1cfd3b9 || >=5.15.162 <5.15.168 || >=6.1.96 <6.1.113 || >=6.6.36 <6.6.57 || >=6.9.7 <6.10 | daf462ff3cde6ecf22b98d9ae770232c10d28de2, b7d22a79ff4e962b8af5ffe623abd1d6c179eb9f, 563e6892e21d6ecabdf62103fc4e7b326d212334, 8e1b72fd74bf9da3b099d09857f4e7f114f38e12, 631083143315d1b192bd7d915b967b37819e88ea, 5.15.168, 6.1.113, 6.6.57, 6.10 |
| Linux/Linuxgeneric | 6.10 | Not reported |
Published upstream
Nov 8, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-50186 records a Unknown severity vulnerability in net: explicitly clear the sk pointer, when pf->create fails. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=78e4aa528a7b1204219d808310524344f627d069 <daf462ff3cde6ecf22b98d9ae770232c10d28de2 || >=893eeba94c40d513cd0fe6539330ebdaea208c0e <b7d22a79ff4e962b8af5ffe623abd1d6c179eb9f || >=454c454ed645fed051216b79622f7cb69c1638f5 <563e6892e21d6ecabdf62103fc4e7b326d212334 || >=6cd4a78d962bebbaf8beb7d2ead3f34120e3f7b2 <8e1b72fd74bf9da3b099d09857f4e7f114f38e12 || >=6cd4a78d962bebbaf8beb7d2ead3f34120e3f7b2 <631083143315d1b192bd7d915b967b37819e88ea || 5dfe2408fd7dc4d2e7ac38a116ff0a37b1cfd3b9 || >=5.15.162 <5.15.168 || >=6.1.96 <6.1.113 || >=6.6.36 <6.6.57 || >=6.9.7 <6.10 | daf462ff3cde6ecf22b98d9ae770232c10d28de2, b7d22a79ff4e962b8af5ffe623abd1d6c179eb9f, 563e6892e21d6ecabdf62103fc4e7b326d212334, 8e1b72fd74bf9da3b099d09857f4e7f114f38e12, 631083143315d1b192bd7d915b967b37819e88ea, 5.15.168, 6.1.113, 6.6.57, 6.10 |
| Linux/Linuxgeneric | 6.10 | Not reported |
Published upstream
Nov 8, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.