[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025070418-CVE-2025-38202-bef0@gregkh>
Date: Fri, 4 Jul 2025 15:37:31 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38202: bpf: Check rcu_read_lock_trace_held() in bpf_map_lookup_percpu_elem()
From: Greg Kroah-Hartman <gregkh@...nel.org>
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.
The Linux kernel CVE team has assigned CVE-2025-38202 to this issue.
Affected and fixed versions
===========================
Fixed in 6.1.142 with commit 2f8c69a72e8ad87b36b8052f789da3cc2b2e186c
Fixed in 6.6.95 with commit 7bf4461f1c97207fda757014690d55a447ce859f
Fixed in 6.12.35 with commit 2d834477bbc1e8b8a59ff8b0c081529d6bed7b22
Fixed in 6.15.4 with commit b522d4d334f206284b1a44b0b0b2f99fd443b39b
Fixed in 6.16-rc1 with commit d4965578267e2e81f67c86e2608481e77e9c8569
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2025-38202
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
kernel/bpf/helpers.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
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
Powered by blists - more mailing lists