CVE-2025-38202: bpf: Check rcu_read_lock_trace_held() in bpf_map_lookup_percpu_elem()
Published Jul 4, 2025
·Updated
bpf: Check rcureadlocktraceheld() in bpfmaplookuppercpuelem()
Affected Software
7 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=5.19<6.1.142
Linux Linux kernel>=6.2<6.6.95
Linux Linux kernel>=6.7<6.12.35
Linux Linux kernel>=6.13<6.15.4
Debian Debian Linux=11.0
Microsoft azl3 kernel 6.6.92.2-2
Event History
Jul 4, 2025
CVE Published
via MITRE·01:37 PM
Data Sourced
via MITRE·01:37 PM
Description
Data Sourced
via Red Hat·02:02 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·02:15 PM
RemedyDescriptionSeverityAffected Software
Aug 7, 2025
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2025-38202?
CVE-2025-38202 is considered a moderate severity vulnerability in the Linux kernel.
2
How do I fix CVE-2025-38202?
To fix CVE-2025-38202, update your Linux kernel to the latest stable version that addresses this vulnerability.
3
What systems are affected by CVE-2025-38202?
CVE-2025-38202 affects various versions of the Linux kernel, particularly those utilizing the BPF subsystem.
4
What is the impact of exploiting CVE-2025-38202?
Exploiting CVE-2025-38202 could lead to instability or unexpected behavior in applications using BPF functionalities.
5
Is there a workaround for CVE-2025-38202?
Currently, the best approach for CVE-2025-38202 is to apply the security patch provided in the latest kernel update.