CVE-2025-38502Exploit(debian / debian_linux)

MEDIUMCVSS 7.1 · HIGH

Exploit discussion active in current signal (1 latest mentions)

Immediate actions

  • Prioritize remediation for debian debian_linux systems immediately
  • Hunt for exploitation attempts and persistence artifacts
  • Increase monitoring for publicly documented tradecraft
  • Track advisory updates for patch or workaround availability

Recommended action window: High priority (within 72h)

NVD 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.

4.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-125

Priority

MEDIUM

Exploitation

NONE

PoC

YES

Patch

AVAILABLE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • debian_linux
  • linux_kernel
  • simatic_cn_4100
  • simatic_cn_4100_firmware

Threat summary

  • Public PoC and exploit tooling are both present
  • 1 mentions across 1 observed day

What's happening

  • Exploit tool or code specified in 1 signal
  • PoC mentioned or linked in 1 signal
  • Technical details provided in 1 signal
  • 1 total mentions across 1 day

Affected systems

Products
debian_linuxlinux_kernelsimatic_cn_4100simatic_cn_4100_firmware

2 versions affected across 4 products

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-09-11: 1PoC Mentioned / Linked · 2026-09-11: 1Exploit Tool / Code · 2026-09-11: 1Technical Details · 2026-09-11: 109-11
Signal classification1 categories
Exploit
1100.0%
Referenced assets1 URL
By indicator
Full discourse1 post
  • abraxas@abraxas_null
    Exploit

    get your pot holders, this dish is HOT! linux LPE 0day (high: 7.8), affecting kernel <= 6.16.0 https://github.com/abraxas/CVE-2025-38502-Linux-LPE https://t.co/i8IjJtAoQs

    Post summary

    A Linux kernel zero‑day LPE (CVE-2025-38502) with a CVSS score of 7.8 is disclosed, and a PoC/functional exploit is available on GitHub, though no active exploitation or patch has been reported.

    01165539
    321 followersView on X
CPE platform detail4 entries

4 of 4 entries

PartVendorProductVersionTarget SWTarget HW
OSdebiandebian_linux11.0--
OSlinuxlinux_kernel---
HWsiemenssimatic_cn_4100---
OSsiemenssimatic_cn_4100_firmware---

Explore more