CVE-2024-38564: bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE
In the Linux kernel, the following vulnerability has been resolved:
bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE
bpf_prog_attach uses attach_type_to_prog_type to enforce proper
attach type for BPF_PROG_TYPE_CGROUP_SKB. link_create uses
bpf_prog_get and relies on bpf_prog_attach_check_attach_type
to properly verify prog_type <> attach_type association.
Add missing attach_type enforcement for the link_create case.
Otherwise, it's currently possible to attach cgroup_skb prog
types to other cgroup hooks.
Security readout for executives and security teams
Plain-English summary
Linux fixed a kernel BPF validation gap. A program type meant for cgroup network packet hooks could be attached to other cgroup hooks through BPF_LINK_CREATE. The public record does not describe observed exploitation, a CVSS score, or concrete business impact, so urgency depends on BPF exposure and kernel update status.
Executive priority
Track and patch through the normal kernel update process, with higher priority for shared compute, container hosts, and systems that intentionally use BPF. Current public evidence does not support emergency handling by itself.
Technical view
CVE-2024-38564 adds missing attach-type enforcement for BPF_PROG_TYPE_CGROUP_SKB in the BPF_LINK_CREATE path. The source says bpf_prog_attach already enforced the prog_type-to-attach_type relationship, but link_create relied on checks that did not prevent cgroup_skb programs from attaching to other cgroup hooks.
Likely exposure
Exposure is Linux-kernel specific. The bundle lists Linux kernel versions and stable commits, but does not map affected distro packages. Systems where workloads can create BPF links or use cgroup BPF functionality deserve earlier review, especially shared or multi-tenant hosts.
Exploitation context
The provided sources do not report active exploitation, public exploit use, or KEV listing. They also do not state required privileges or full impact. Treat exploitation status as unconfirmed and avoid assuming remote reachability from the available evidence.
Researcher notes
The key behavior is missing attach-type validation in BPF_LINK_CREATE, not bpf_prog_attach. Validate by reviewing kernel lineage and the presence of the stable commits. The source bundle does not provide impact classification, CWE, CVSS, exploitability prerequisites, or distro backport details.
Mitigation direction
Update to a vendor kernel containing the referenced stable fixes.
Check Linux distribution advisories for package-specific fixed versions.
Prioritize shared systems that expose BPF or cgroup functionality to workloads.
Restrict unnecessary BPF capability exposure according to existing hardening policy.
Validation and detection
Inventory Linux kernel versions across servers, containers hosts, and appliances.
Compare installed kernels with vendor advisories for CVE-2024-38564.
Confirm whether BPF and cgroup BPF features are available to workloads.
Verify patched hosts are booted into the updated kernel.
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-38564 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.