NVD / CVE Program· CNA Linux

CVE-2024-50186: net: explicitly clear the sk pointer, when pf->create fails

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 5.15.168, 563e6892e21d6ecabdf62103fc4e7b326d212334, 6.1.113; cbl2 kernel 5.15.167.1-2 on CBL Mariner 2.0 5.15.173.1-1; cbl2 kernel 5.15.167.1-2 on CBL-Mariner 2.0 5.15.173.1-1.

Low priority for now. Upgrade to Linux Linux 5.15.168, 563e6892e21d6ecabdf62103fc4e7b326d212334, 6.1.113; cbl2 kernel 5.15.167.1-2 on CBL Mariner 2.0 5.15.173.1-1; cbl2 kernel 5.15.167.1-2 on CBL-Mariner 2.0 5.15.173.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

BDU:2025-03471

Published: Nov 8, 2024
Updated: Aug 5, 2026
EPSS: 0.2% · 14th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.8
CNA · Linux: 7.8; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel5.15.162 and later · before 5.15.168
linux linux kernel6.1.96 and later · before 6.1.113
linux linux kernel6.6.36 and later · before 6.6.57
linux linux kernel6.9.7 and later · before 6.10
linux linux kernel6.10 and later · before 6.11.4
linux linux kernel6.12

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 5dfe2408fd7dc4d2e7ac38a116ff0a37b1cfd3b9, 6.10affected
- 78e4aa528a7b1204219d808310524344f627d069 and later · before daf462ff3cde6ecf22b98d9ae770232c10d28de2affected · git
- 893eeba94c40d513cd0fe6539330ebdaea208c0e and later · before b7d22a79ff4e962b8af5ffe623abd1d6c179eb9faffected · git
- 454c454ed645fed051216b79622f7cb69c1638f5 and later · before 563e6892e21d6ecabdf62103fc4e7b326d212334affected · git
- 6cd4a78d962bebbaf8beb7d2ead3f34120e3f7b2 and later · before 8e1b72fd74bf9da3b099d09857f4e7f114f38e12affected · git
- 6cd4a78d962bebbaf8beb7d2ead3f34120e3f7b2 and later · before 631083143315d1b192bd7d915b967b37819e88eaaffected · git
- 5.15.162 and later · before 5.15.168affected · semver
- 6.1.96 and later · before 6.1.113affected · semver
- 6.6.36 and later · before 6.6.57affected · semver
- 6.9.7 and later · before 6.10affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.115-1	6.1.115-1
Debian:13	linux	before 6.11.4-1	6.11.4-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2024-50184Nov 8, 2024 · virtio_pmem: Check device status before requesting flush
22Monitor
← EarlierCVE-2024-50185Nov 8, 2024 · mptcp: handle consistently DSS corruption
22Monitor
Later →CVE-2024-50187Nov 8, 2024 · drm/vc4: Stop the active perfmon before being destroyed
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	5.15.168	Vendor (CNA)
Linux Linux	563e6892e21d6ecabdf62103fc4e7b326d212334	Vendor (CNA)
Linux Linux	6.1.113	Vendor (CNA)
Linux Linux	6.10	Vendor (CNA)
Linux Linux	6.6.57	Vendor (CNA)
Linux Linux	631083143315d1b192bd7d915b967b37819e88ea	Vendor (CNA)
Linux Linux	8e1b72fd74bf9da3b099d09857f4e7f114f38e12	Vendor (CNA)
Linux Linux	b7d22a79ff4e962b8af5ffe623abd1d6c179eb9f	Vendor (CNA)
Linux Linux	daf462ff3cde6ecf22b98d9ae770232c10d28de2	Vendor (CNA)
cbl2 kernel 5.15.167.1-2 on CBL Mariner 2.0	5.15.173.1-1 · CBL-Mariner Releases	Microsoft (MSRC)
cbl2 kernel 5.15.167.1-2 on CBL-Mariner 2.0	5.15.173.1-1 · CBL-Mariner Releases	Microsoft (MSRC)
cbl2 kernel 5.15.173.1-1 on CBL Mariner 2.0	5.15.173.1-1 · CBL-Mariner Releases	Microsoft (MSRC)
debian:linux	6.1.115-1 · Debian:12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:09 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/563e6892e21d6ecabdf62103fc4e7b326d212334

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records