LiveActive security incident?Get immediate response
CVE Record

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

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.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in the Linux kernel’s packet-socket code can leave a freed object referenced by another structure. A low-privileged local attacker who can reach the vulnerable path could potentially crash the system or compromise confidentiality and integrity. The supplied CVSS 3.1 score is 7.8.

Executive priority

Treat this as a high-priority local privilege-boundary risk. Patch promptly through supported distribution channels, prioritizing shared systems and hosts where lower-privileged users can execute local code. Emergency internet-edge action is not indicated because the supplied evidence describes local access and no known active exploitation.

Technical view

In packet_create(), sock_init_data() attaches the allocated sk object to sock. A subsequent error frees sk without clearing the attached reference, creating a use-after-free condition. Later code may dereference that stale pointer. The CVSS vector indicates local access, low privileges, low complexity, no user interaction, and potentially high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is plausible on systems running vendor kernels containing the vulnerable packet_create() logic where a low-privileged local user can access the relevant AF_PACKET path. The bundle’s version entries are ambiguous, so kernel versions alone should not be treated as a definitive exposure range.

Exploitation context

The supplied record does not identify known active exploitation, and the CVE is not marked as present in KEV. Exploitation requires local, low-privileged access according to the supplied CVSS vector. No remote attack path is documented in the source bundle.

Researcher notes

The critical condition is the error path after sock_init_data(): sk becomes reachable through sock, is freed, and remains referenced. Assessment should focus on whether the deployed vendor kernel contains the faulty lifetime handling or an applicable stable backport. The bundle provides multiple fix commits but no dependable normalized affected range.

Mitigation direction

  • Apply a vendor-supported kernel update incorporating the applicable Linux stable fix.
  • Reboot affected systems into the updated kernel after installation.
  • Consult the operating-system vendor for supported mitigations if immediate updating is impossible.
  • Prioritize systems accessible to untrusted or lower-privileged local users.

Validation and detection

  • Inventory running kernel versions across Linux hosts.
  • Map each vendor kernel build to its security advisory or applicable stable fix commit.
  • Confirm updated hosts are running the new kernel after reboot.
  • Review vendor advisories because the supplied affected-version data is ambiguous.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-416: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-56606 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
3Timeline events
2ADP providers
10Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-56606Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxb013840810c221f2b0cf641d01531526052dc1fb, b013840810c221f2b0cf641d01531526052dc1fb, b013840810c221f2b0cf641d01531526052dc1fb, b013840810c221f2b0cf641d01531526052dc1fb, b013840810c221f2b0cf641d01531526052dc1fb, b013840810c221f2b0cf641d01531526052dc1fb, b013840810c221f2b0cf641d01531526052dc1fbunaffected
LinuxLinux3.14, 0, 5.4.287, 5.10.231, 5.15.174, 6.1.120, 6.6.66, 6.12.5, 6.13affected
Weakness

CWE details

CWE-416

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs