CVE-2025-38502

bpf: Fix oob access in cgroup local storage

HIGH
7.1
CVSS Score
Published: August 16, 2025 at 09:34 AM UTC
Updated: October 15, 2026 at 10:18 PM UTC
3 products affected across 3 vendorsLinux KernelDebian LinuxSIMATIC Cn 4100 Firmware· also runs on 1 platform

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
HIGH7.1
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix oob access in cgroup local storage Lonial reported that an out-of-bounds access in cgroup local storage can be crafted via tail calls. Given two programs each utilizing a cgroup local storage with a different value size, and one program doing a tail call into the other. The verifier will validate each of the indivial programs just fine. However, in the runtime context the bpf_cg_run_ctx holds an bpf_prog_array_item which contains the BPF program as well as any cgroup local storage flavor the program uses. Helpers such as bpf_get_local_storage() pick this up from the runtime context: ctx = container_of(current->bpf_ctx, struct bpf_cg_run_ctx, run_ctx); storage = ctx->prog_item->cgroup_storage[stype]; if (stype == BPF_CGROUP_STORAGE_SHARED) ptr = &READ_ONCE(storage->buf)->data[0]; else ptr = this_cpu_ptr(storage->percpu_buf); For the second program which was called from the originally attached one, this means bpf_get_local_storage() will pick up the former program's map, not its own. With mismatching sizes, this can result in an unintended out-of-bounds access. To fix this issue, we need to extend bpf_map_owner with an array of storage_cookie[] to match on i) the exact maps from the original program if the second program was using bpf_get_local_storage(), or ii) allow the tail call combination if the second program was not using any of the cgroup local storage maps.

Affected

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

5.16 ≤ v < 6.1.1515.9 ≤ v < 5.15.1926.13 ≤ v < 6.16.16.2 ≤ v < 6.6.1056.7 ≤ v < 6.12.465.97d9c3427894fe70d1347b4820476bf37736d2ff0
Vendor states this is fixed in 19341d5c59e8c7e8528e40f8663e99d67810473c (fixed)
Vendor states this is fixed in 41688d1fc5d163a6c2c0e95c0419e2cb31a44648 (fixed)
Vendor states this is fixed in 66da7cee78590259b400e51a70622ccd41da7bb2 (fixed)
Vendor states this is fixed in 7acfa07c585e3d7a64654d38f0a5c762877d0b9b (fixed)
Vendor states this is fixed in abad3d0bad72a52137e0c350c59542d75ae4f513 (fixed)
Vendor states this is fixed in c1c74584b9b4043c52e41fec415226e582d266a3 (fixed)
Vendor states this is fixed in 5.15.192 (unaffected)
Vendor states this is fixed in 5.9 (unaffected)
Vendor states this is fixed in 6.1.151 (unaffected)
Vendor states this is fixed in 6.12.46 (unaffected)
Vendor states this is fixed in 6.16.1 (unaffected)
Vendor states this is fixed in 6.17 (unaffected)
Vendor states this is fixed in 6.6.105 (unaffected)
v < 5.0
Affected range stops below 5.0, so it looks safe — our inference, not a vendor statement
siemens-simatic-cn-4100 (same device)

Runs on — not affected

The affected product only carries this flaw when running on these platforms. The platforms themselves are not vulnerable.

Affected range stops below V5.0, so it looks safe — our inference, not a vendor statement

References (8)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/19341d5c59e8c7e8528e40f8663e99d67810473c
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/41688d1fc5d163a6c2c0e95c0419e2cb31a44648
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/66da7cee78590259b400e51a70622ccd41da7bb2
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/7acfa07c585e3d7a64654d38f0a5c762877d0b9b
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/abad3d0bad72a52137e0c350c59542d75ae4f513
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/c1c74584b9b4043c52e41fec415226e582d266a3
Mailing ListThird Party Advisory
Source: af854a3a-2127-422b-91ae-364da2661108
https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Third Party Advisory
Source: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
https://cert-portal.siemens.com/productcert/html/ssa-032379.html

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal 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
HIGH
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-125

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