CVE-2025-38202 [Medium] | Security Vulnerability in Linux Kernel

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-04-30	0.02%	0.07%	+0.05%
2	2025-07-05	—	0.02%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-04-30

0.02%

0.07%

+0.05%

2025-07-05

—

0.02%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

3.6

[email protected]

OS Trackers for CVE-2025-38202

vendor	priority	summary	link
`debian`	unimportant	CVE-2025-38202 unimportant priority: Debian including 2 source packages (linux, linux-6.1), 6 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 6.	https://security-tracker.debian.org/tracker/CVE-2025-38202
`redhat`	low	—	https://access.redhat.com/security/cve/CVE-2025-38202
`suse`	medium	CVE-2025-38202 severity moderate: SUSE including 432 source package names (2.1.3-6.67:kernel-default-base-6.4.0-32.1.21.10, 2.1.3-7.44:kernel-default-6.4.0-32.1, …), 866 product×package rows across 180 product lines (Container suse/sl-micro/6.0/base-os-container, Container suse/sl-micro/6.0/kvm-os-container, … (180 product lines)): Fixed 476, Known Affected 231, Known Not Affected 159.	https://www.suse.com/security/cve/CVE-2025-38202/
`ubuntu`	medium	CVE-2025-38202 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1551 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1145, ignored 168, released 138, needed 77, not-affected 20, needs-triage 2, pending 1.	https://ubuntu.com/security/CVE-2025-38202

Affected software / configurations for CVE-2025-38202

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 5.19, < 6.1.142	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.2, < 6.6.95	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.7, < 6.12.35	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.13, < 6.15.4	cpe:2.3:o:linux:linux_kernel::::::::
debian	debian_linux	11.0	cpe:2.3:o:debian:debian_linux:11.0:::::::*

References for CVE-2025-38202

URL	Tags
https://git.kernel.org/stable/c/2d834477bbc1e8b8a59ff8b0c081529d6bed7b22	Patch
https://git.kernel.org/stable/c/2f8c69a72e8ad87b36b8052f789da3cc2b2e186c	Patch
https://git.kernel.org/stable/c/7bf4461f1c97207fda757014690d55a447ce859f	Patch
https://git.kernel.org/stable/c/b522d4d334f206284b1a44b0b0b2f99fd443b39b	Patch
https://git.kernel.org/stable/c/d4965578267e2e81f67c86e2608481e77e9c8569	Patch
https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html	Mailing List Third Party Advisory

URL

CVE-2025-38202 | bpf: Check rcu_read_lock_trace_held() in bpf_map_lookup_percpu_elem()

Exploit prediction scoring system (EPSS) score for CVE-2025-38202

Common vulnerability scoring system (CVSS) metrics for CVE-2025-38202

Weakness enumeration for CVE-2025-38202

OS Trackers for CVE-2025-38202

Affected software / configurations for CVE-2025-38202

References for CVE-2025-38202