CVE-2024-56602: net: ieee802154: do not leave a dangling sk pointer in ieee802154_create()
In the Linux kernel, the following vulnerability has been resolved:
net: ieee802154: do not leave a dangling sk pointer in ieee802154_create()
sock_init_data() attaches the allocated sk object to the provided sock
object. If ieee802154_create() fails later, the allocated sk object is
freed, but the dangling pointer remains in the provided sock object, which
may allow use-after-free.
Clear the sk pointer in the sock object on error.
Security readout for executives and security teams
Plain-English summary
A Linux kernel error path can leave a reference to memory that has already been freed. A locally authenticated, low-privilege user may be able to trigger this condition without user interaction. The CVSS assessment models potentially severe confidentiality, integrity, and availability consequences, although the supplied sources do not document a demonstrated exploit outcome.
Executive priority
Treat this as a high-priority kernel maintenance issue, especially on shared, embedded, or radio-enabled Linux systems with untrusted local access. It does not currently warrant emergency response based on active exploitation evidence. Expedite exposure inventory and vendor-backed patching while preserving normal kernel update testing and reboot controls.
Technical view
In ieee802154_create(), sock_init_data() associates an allocated socket structure with a sock object. If later initialization fails, that structure is freed without clearing the sock object's sk pointer, creating a potential use-after-free. The upstream correction clears the pointer on the error path. CVE-2024-56602 is classified as CWE-416 with CVSS 3.1 score 7.8.
Likely exposure
Exposure is limited to vulnerable Linux kernels where the IEEE 802.15.4 socket path is available and reachable by a low-privilege local user. This is not scored as a network attack. The supplied version extraction is insufficiently clear for reliable package-level decisions; distribution backports and commit ancestry must be checked.
Exploitation context
The source bundle marks this CVE as absent from CISA KEV and provides no evidence of active exploitation or a public proof of concept. Exploitation requires local access with low privileges according to the CVSS vector. Trigger reliability, necessary kernel configuration, and practical impact are not established by the supplied evidence.
Researcher notes
Important unknowns include the precise affected package ranges, required kernel configuration, controllability of the failure path, and whether exploitation can progress beyond a crash. The duplicated commit identifier and ambiguous version list reduce confidence in automated matching. Validate fixes through vendor backport records or comparison with the cited stable commits.
Mitigation direction
Apply a Linux distribution kernel update incorporating the CVE-2024-56602 stable fix or an equivalent vendor backport.
Ensure systems boot into the updated kernel; installing a package alone may leave the vulnerable kernel running.
Prioritize systems exposing IEEE 802.15.4 functionality to untrusted local users or processes.
If updating is delayed, consult distribution guidance; the sources name no alternative mitigation.
Validation and detection
Inventory running kernel builds across Linux systems, including embedded and IEEE 802.15.4-capable devices.
Map each build to its distribution advisory and backport status rather than comparing version numbers alone.
Verify the installed update contains an equivalent correction that clears sock->sk on the failure path.
After maintenance, confirm every system is running the updated kernel.
Document whether IEEE 802.15.4 kernel support and local socket access are present.
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.
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.