CVE-2024-38566: bpf: Fix verifier assumptions about socket->sk
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix verifier assumptions about socket->sk
The verifier assumes that 'sk' field in 'struct socket' is valid
and non-NULL when 'socket' pointer itself is trusted and non-NULL.
That may not be the case when socket was just created and
passed to LSM socket_accept hook.
Fix this verifier assumption and adjust tests.
Security readout for executives and security teams
Plain-English summary
This Linux kernel flaw involves a mistaken eBPF verifier assumption about newly accepted sockets. The sources do not provide CVSS, business impact, or exploitation evidence. Treat it as a kernel maintenance risk where affected systems should receive the relevant stable kernel updates.
Executive priority
Track this as a kernel patching item rather than an emergency unless vendor guidance adds severity or exploitation evidence. Prioritize normal expedited maintenance for exposed or multi-tenant Linux infrastructure.
Technical view
The eBPF verifier assumed struct socket->sk was valid and non-NULL when the socket pointer was trusted. The CVE states this can be false for a socket just created and passed to the LSM socket_accept hook. Kernel stable commits correct the verifier assumption and adjust tests.
Likely exposure
Exposure is most plausible on Linux systems running affected kernel versions with eBPF and LSM socket_accept hook paths available. The source bundle identifies Linux kernel version ranges beginning at 6.4 and fixed through listed stable commits, but gives no distribution package mapping.
Exploitation context
CISA KEV is false in the provided bundle, and no cited source states active exploitation or public exploitation. The sources also do not describe prerequisites, exploit reliability, or required privileges, so practical exploitability remains unclear from this evidence.
Researcher notes
Evidence is limited to the Linux CVE description and stable commit references. Focus review on verifier treatment of socket->sk in LSM socket_accept contexts and downstream kernel backports. Do not assume impact class beyond the provided verifier flaw.
Mitigation direction
Update affected Linux kernels to builds containing the referenced stable fixes.
Use distribution vendor advisories to map fixed kernel packages to deployed systems.
Prioritize internet-facing, multi-tenant, container-hosting, and developer systems using recent kernels.
If immediate patching is delayed, review vendor guidance for temporary risk reduction.
Validation and detection
Inventory Linux kernel versions across servers, containers hosts, and appliances.
Map running kernels against vendor advisories for CVE-2024-38566.
Confirm deployed kernel builds include the referenced stable commits or downstream backports.
Review eBPF and LSM usage where operationally relevant.
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.
cve · low confidence lookup
CVE-2024-38566 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.