# CVE-2024-56720: bpf, sockmap: Several fixes to bpf_msg_pop_data

> A memory corruption vulnerability in the Linux kernel's BPF sockmap allows attackers to potentially execute code or cause a denial of service.

- **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:** 29 Dec 2024
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-55259, AZL-55265, BELL-CVE-2024-56720, DEBIAN-CVE-2024-56720, GHSA-4x48-ph6h-wfmf, UBUNTU-CVE-2024-56720

## What is CVE-2024-56720?

CVE-2024-56720 is a high-severity memory corruption vulnerability in Linux kernel, published on 29 Dec 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, sockmap: Several fixes to bpf_msg_pop_data

Several fixes to bpf_msg_pop_data,
1. In sk_msg_shift_left, we should put_page
2. if (len == 0), return early is better
3. pop the entire sk_msg (last == msg->sg.size) should be supported
4. Fix for the value of variable "a"
5. In sk_msg_shift_left, after shifting, i has already pointed to the next
element. Addtional sk_msg_iter_var_next may result in BUG.

Weakness: CWE-193 (Off-by-one Error), CWE-401 (Missing Release of Memory after Effective Lifetime)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-56720 being exploited?

There is no known exploitation of CVE-2024-56720 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-56720 and fix it if it is affected.

What it is: CVE-2024-56720 is a high-severity memory corruption vulnerability in Linux kernel, published on 29 Dec 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-56720 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-56720/ (Markdown: https://insights.sbomify.com/CVE-2024-56720/index.md)
```

## Sources

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

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