Answer in brief
CVE-2023-52676 records a High severity (CVSS 7.8) vulnerability in bpf: Guard stack limits against 32bit overflow. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=01f810ace9ed37255f27608a0864abebccf0aab3 <ad140fc856f0b1d5e2215bcb6d0cc247a86805a2 || >=01f810ace9ed37255f27608a0864abebccf0aab3 <e5ad9ecb84405637df82732ee02ad741a5f782a6 || >=01f810ace9ed37255f27608a0864abebccf0aab3 <1d38a9ee81570c4bd61f557832dead4d6f816760 || f3c4b01689d392373301e6e60d1b02c5b4020afc || d1b725ea5d104caea250427899f4e2e3ab15b4fc || >=5.10.33 <5.11 || >=5.11.17 <5.12 | ad140fc856f0b1d5e2215bcb6d0cc247a86805a2, e5ad9ecb84405637df82732ee02ad741a5f782a6, 1d38a9ee81570c4bd61f557832dead4d6f816760, 5.11, 5.12 |
| Linux/Linuxgeneric | 5.12 | Not reported |
Published upstream
May 17, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2023-52676 records a High severity (CVSS 7.8) vulnerability in bpf: Guard stack limits against 32bit overflow. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=01f810ace9ed37255f27608a0864abebccf0aab3 <ad140fc856f0b1d5e2215bcb6d0cc247a86805a2 || >=01f810ace9ed37255f27608a0864abebccf0aab3 <e5ad9ecb84405637df82732ee02ad741a5f782a6 || >=01f810ace9ed37255f27608a0864abebccf0aab3 <1d38a9ee81570c4bd61f557832dead4d6f816760 || f3c4b01689d392373301e6e60d1b02c5b4020afc || d1b725ea5d104caea250427899f4e2e3ab15b4fc || >=5.10.33 <5.11 || >=5.11.17 <5.12 | ad140fc856f0b1d5e2215bcb6d0cc247a86805a2, e5ad9ecb84405637df82732ee02ad741a5f782a6, 1d38a9ee81570c4bd61f557832dead4d6f816760, 5.11, 5.12 |
| Linux/Linuxgeneric | 5.12 | Not reported |
Published upstream
May 17, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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
Quoted source text, attributed separately from HOL analysis.