CVE-2023-52676

bpf: Guard stack limits against 32bit overflow

MEDIUM
5.5
CVSS Score
Published: May 17, 2024 at 02:24 PM UTC
Updated: September 14, 2026 at 12:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 5.11.175.10.33 ≤ v < 5.10.2705.10.33 ≤ v < 5.115.11.17 ≤ v < 5.125.11.17 ≤ v < 6.6.145.12 ≤ v < 5.15.2215.12 ≤ v < 6.1.1885.12 ≤ v < 6.6.145.12 ≤ v < 6.7.25.12 ≤ v < 6.86.7 ≤ v < 6.7.21f810ace9ed37255f27608a864abebccf0aab35.10.335.11.175.12d1b725ea5d104caea250427899f4e2e3ab15b4fcf3c4b01689d392373301e6e60d1b02c5b4020afc
Vendor states this is fixed in 1d38a9ee81570c4bd61f557832dead4d6f816760 (fixed)
Vendor states this is fixed in 4ba97610399e83d29d1086a0827d33172539b49b (fixed)
Vendor states this is fixed in ad140fc856f0b1d5e2215bcb6d0cc247a86805a2 (fixed)
Vendor states this is fixed in ad1754f86a87fe74912fb542b23ff24ada4e3307 (fixed)
Vendor states this is fixed in e160b2ed94a20fa940369ebd914277f88005e70d (fixed)
Vendor states this is fixed in e5ad9ecb84405637df82732ee02ad741a5f782a6 (fixed)
Vendor states this is fixed in 5.10.270 (unaffected)
Affected range stops below 5.11, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.12 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.6.14 (unaffected)
Vendor states this is fixed in 6.7.2 (unaffected)
Vendor states this is fixed in 6.8 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-190

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card