Skip to main content
VulnerabilityPublished Updated

CVE-2025-38202: Linux kernel · bpf: Check rcu_read_lock_trace_held() in bpf_map_lookup_percpu_elem()

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in d4965578267e2e81f67c86e2608481e77e9c8569 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:04 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in d4965578267e2e81f67c86e2608481e77e9c8569, b522d4d334f206284b1a44b0b0b2f99fd443b39b, 7bf4461f1c97207fda757014690d55a447ce859f +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 07343110b293456d30393e89b86c4dee1ac051c8, < d4965578267e2e81f67c86e2608481e77e9c8569
Fixed in
  • d4965578267e2e81f67c86e2608481e77e9c8569
LinuxLinuxAffected
  • ≥ 07343110b293456d30393e89b86c4dee1ac051c8, < b522d4d334f206284b1a44b0b0b2f99fd443b39b
Fixed in
  • b522d4d334f206284b1a44b0b0b2f99fd443b39b
LinuxLinuxAffected
  • ≥ 07343110b293456d30393e89b86c4dee1ac051c8, < 7bf4461f1c97207fda757014690d55a447ce859f
Fixed in
  • 7bf4461f1c97207fda757014690d55a447ce859f
LinuxLinuxAffected
  • ≥ 07343110b293456d30393e89b86c4dee1ac051c8, < 2f8c69a72e8ad87b36b8052f789da3cc2b2e186c
Fixed in
  • 2f8c69a72e8ad87b36b8052f789da3cc2b2e186c
LinuxLinuxAffected
  • ≥ 07343110b293456d30393e89b86c4dee1ac051c8, < 2d834477bbc1e8b8a59ff8b0c081529d6bed7b22
Fixed in
  • 2d834477bbc1e8b8a59ff8b0c081529d6bed7b22
LinuxLinuxAffected
  • =5.19
Fixed in–

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.

References

Community reviews

Loading reviews…