# CVE-2024-38564: bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE

> Attackers can bypass attach type checks to attach cgroup_skb programs to unauthorized cgroup hooks, potentially escalating privileges or bypassing security controls.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jun 2024
- **Updated:** 27 Oct 2026
- **Also known as:** AZL-68606, BELL-CVE-2024-38564, DEBIAN-CVE-2024-38564, GHSA-h2jq-7w25-hghw, RHSA-2024:10945, RHSA-2024:10946, ROOT-OS-DEBIAN-11-CVE-2024-38564, ROOT-OS-DEBIAN-12-CVE-2024-38564, ROOT-OS-UBUNTU-2204-CVE-2024-38564, UBUNTU-CVE-2024-38564

## What is CVE-2024-38564?

CVE-2024-38564 is a high-severity missing authorization vulnerability in Linux kernel, published on 19 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2024-38564?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bpftool-debuginfo` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:7.0.0-284.96.1.el9_2 |
| `kernel-64k-debug-debuginfo` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-64k-debug-devel` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-64k-debug-devel-matched` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-64k-debuginfo` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-64k-devel` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-64k-devel-matched` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-debug-debuginfo` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-debug-devel` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-debug-devel-matched` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-debuginfo` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-debuginfo-common-aarch64` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-debuginfo-common-ppc64le` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-debuginfo-common-s390x` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-debuginfo-common-x86_64` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-devel` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-devel-matched` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-tools-debuginfo` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-zfcpdump-debuginfo` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-zfcpdump-devel` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-zfcpdump-devel-matched` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:5.14.0-284.96.1.el9_2 |
| `perf` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:5.14.0-284.96.1.el9_2 |
| `perf-debuginfo` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:5.14.0-284.96.1.el9_2 |
| `python3-perf-debuginfo` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:5.14.0-284.96.1.el9_2 |
| `rtla` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:5.14.0-284.96.1.el9_2 |
| `bpftool` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:7.0.0-284.96.1.el9_2 |
| `bpftool-debuginfo` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:7.0.0-284.96.1.el9_2 |
| `kernel` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-64k` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-64k-core` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-64k-debug` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-64k-debug-core` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-64k-debug-debuginfo` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-64k-debug-modules` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-64k-debug-modules-core` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-64k-debug-modules-extra` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-64k-debuginfo` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-64k-modules` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-64k-modules-core` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:5.14.0-284.96.1.el9_2 |
| `kernel-64k-modules-extra` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:5.14.0-284.96.1.el9_2 |

Products: Linux kernel.

## How do I fix CVE-2024-38564?

Apply the vendor's patch.

## Is CVE-2024-38564 being exploited?

There is no known exploitation of CVE-2024-38564 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-38564 and fix it if it is affected.

What it is: CVE-2024-38564 is a high-severity missing authorization vulnerability in Linux kernel, published on 19 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-38564 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-38564/ (Markdown: https://insights.sbomify.com/CVE-2024-38564/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-38564
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-38564
- OSV: https://osv.dev/vulnerability/CVE-2024-38564

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-38564/
Summaries are generated and may contain mistakes; the official description above is the record.