NVD / CVE Program· CNA Linux

CVE-2024-56606: af_packet: avoid erroring out after sock_init_data() in packet_create()

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.24% (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 132e615bb1d7cdec2d3cfbdec2efa630e923fd21, 157f08db94123e2ba56877dd0ac88908b13a5dd0, 1dc1e1db927056cb323296e2294a855cd003dfe7; azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 6.6.76.1-1; azl3 kernel 6.6.76.1-1 on Azure Linux 3.0 6.6.76.1-1.

Low priority for now. Upgrade to Linux Linux 132e615bb1d7cdec2d3cfbdec2efa630e923fd21, 157f08db94123e2ba56877dd0ac88908b13a5dd0, 1dc1e1db927056cb323296e2294a855cd003dfe7; azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 6.6.76.1-1; azl3 kernel 6.6.76.1-1 on Azure Linux 3.0 6.6.76.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: af_packet: avoid erroring out after sock_init_data() in packet_create() After sock_init_data() the allocated sk object is attached to the provided sock object. On error, packet_create() frees the sk object leaving the dangling pointer in the sock object on return. Some other code may try to use this pointer and cause use-after-free.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

BDU:2025-04675

Published: Dec 27, 2024
Updated: Oct 15, 2026
EPSS: 0.2% · 16th 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.

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 kernelbefore 5.4.287
linux linux kernel5.5 and later · before 5.10.231
linux linux kernel5.11 and later · before 5.15.174
linux linux kernel5.16 and later · before 6.1.120
linux linux kernel6.2 and later · before 6.6.66
linux linux kernel6.7 and later · before 6.12.5

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
- 3.14affected
- b013840810c221f2b0cf641d01531526052dc1fb and later · before 71b22837a5e55ac27d6a14b9cdf2326587405c4faffected · git
- b013840810c221f2b0cf641d01531526052dc1fb and later · before 1dc1e1db927056cb323296e2294a855cd003dfe7affected · git
- b013840810c221f2b0cf641d01531526052dc1fb and later · before 132e615bb1d7cdec2d3cfbdec2efa630e923fd21affected · git
- b013840810c221f2b0cf641d01531526052dc1fb and later · before a6cf750b737374454a4e03a5ed449a3eb0c96414affected · git
- b013840810c221f2b0cf641d01531526052dc1fb and later · before 157f08db94123e2ba56877dd0ac88908b13a5dd0affected · git
- b013840810c221f2b0cf641d01531526052dc1fb and later · before fd09880b16d33aa5a7420578e01cd79148fa9829affected · git
- b013840810c221f2b0cf641d01531526052dc1fb and later · before 46f2a11cb82b657fd15bab1c47821b635e03838baffected · git
- before 3.14not affected · semver
- 5.4.287 and later · up to and including 5.4.*not affected · 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.123-1	6.1.123-1
Debian:13	linux	before 6.12.5-1	6.12.5-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-56600Dec 27, 2024 · net: inet6: do not leave a dangling sk pointer in inet6_create()
31Monitor
← EarlierCVE-2024-56601Dec 27, 2024 · net: inet: do not leave a dangling sk pointer in inet_create()
31Monitor
Later →CVE-2024-56609Dec 27, 2024 · wifi: rtw88: use ieee80211_purge_tx_queue() to purge TX skb
31Monitor

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	132e615bb1d7cdec2d3cfbdec2efa630e923fd21	Vendor (CNA)
Linux Linux	157f08db94123e2ba56877dd0ac88908b13a5dd0	Vendor (CNA)
Linux Linux	1dc1e1db927056cb323296e2294a855cd003dfe7	Vendor (CNA)
Linux Linux	46f2a11cb82b657fd15bab1c47821b635e03838b	Vendor (CNA)
Linux Linux	71b22837a5e55ac27d6a14b9cdf2326587405c4f	Vendor (CNA)
Linux Linux	a6cf750b737374454a4e03a5ed449a3eb0c96414	Vendor (CNA)
Linux Linux	fd09880b16d33aa5a7420578e01cd79148fa9829	Vendor (CNA)
azl3 kernel 6.6.64.2-9 on Azure Linux 3.0	6.6.76.1-1 · CBL-Mariner Releases	Microsoft (MSRC)
azl3 kernel 6.6.76.1-1 on Azure Linux 3.0	6.6.76.1-1 · CBL-Mariner Releases	Microsoft (MSRC)
cbl2 kernel 5.15.173.1-2 on CBL Mariner 2.0	5.15.176.3-1 · CBL-Mariner Releases	Microsoft (MSRC)
cbl2 kernel 5.15.173.1-2 on CBL-Mariner 2.0	5.15.176.3-1 · CBL-Mariner Releases	Microsoft (MSRC)
cbl2 kernel 5.15.176.3-1 on CBL Mariner 2.0	5.15.176.3-1 · CBL-Mariner Releases	Microsoft (MSRC)
debian:linux	6.1.123-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:11 PM UTC

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

References

git.kernel.org/stable/c/132e615bb1d7cdec2d3cfbdec2efa630e923fd21

Show all references (10 more)

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

All records