# CVE-2023-52676: bpf: Guard stack limits against 32bit overflow

> Integer overflow in Linux kernel BPF verifier stack limit checks allows attackers to bypass bounds, potentially leading to code execution or privilege escalation.

- **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:** 17 May 2024
- **Updated:** 14 Sep 2026
- **Also known as:** AZL-67731, BELL-CVE-2023-52676, DEBIAN-CVE-2023-52676, GHSA-x25x-hhpj-pjqp, ROOT-OS-DEBIAN-11-CVE-2023-52676, ROOT-OS-DEBIAN-12-CVE-2023-52676, ROOT-OS-UBUNTU-2204-CVE-2023-52676, UBUNTU-CVE-2023-52676

## What is CVE-2023-52676?

CVE-2023-52676 is a high-severity vulnerability in Linux kernel, published on 17 May 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: Guard stack limits against 32bit overflow

This patch promotes the arithmetic around checking stack bounds to be
done in the 64-bit domain, instead of the current 32bit. The arithmetic
implies adding together a 64-bit register with a int offset. The
register was checked to be below 1<<29 when it was variable, but not
when it was fixed. The offset either comes from an instruction (in which
case it is 16 bit), from another register (in which case the caller
checked it to be below 1<<29 [1]), or from the size of an argument to a
kfunc (in which case it can be a u32 [2]). Between the register being
inconsistently checked to be below 1<<29, and the offset being up to an
u32, it appears that we were open to overflowing the `int`s which were
currently used for arithmetic.

[1] https://github.com/torvalds/linux/blob/815fb87b753055df2d9e50f6cd80eb10235fe3e9/kernel/bpf/verifier.c#L7494-L7498
[2] https://github.com/torvalds/linux/blob/815fb87b753055df2d9e50f6cd80eb10235fe3e9/kernel/bpf/verifier.c#L11904

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2023-52676?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2023-52676?

Apply the vendor's patch.

## Is CVE-2023-52676 being exploited?

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

What it is: CVE-2023-52676 is a high-severity vulnerability in Linux kernel, published on 17 May 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-2023-52676 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-2023-52676/ (Markdown: https://insights.sbomify.com/CVE-2023-52676/index.md)
```

## Sources

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

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