CVE-2023-52621: bpf: Check rcu_read_lock_trace_held() before calling bpf map helpers
bpf: Check rcureadlocktraceheld() before calling bpf map helpers
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1 - Upgrade
Upgrade
redhat/kernelto a version that resolves this vulnerability.Fixed in 6.1.77 - Upgrade
Upgrade
redhat/kernelto a version that resolves this vulnerability.Fixed in 6.6.16 - Upgrade
Upgrade
redhat/kernelto a version that resolves this vulnerability.Fixed in 6.7.4 - Upgrade
Upgrade
redhat/kernelto a version that resolves this vulnerability.Fixed in 6.8 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 5.15.182.1-1
Event History
Frequently Asked Questions
What is the severity of CVE-2023-52621?
The severity of CVE-2023-52621 is classified as moderate.
How do I fix CVE-2023-52621?
To fix CVE-2023-52621, update the Linux kernel to versions 6.1.77, 6.6.16, 6.7.4, 6.8, or newer versions as specified.
Which systems are affected by CVE-2023-52621?
CVE-2023-52621 affects specific versions of the Linux kernel, including those maintained by Red Hat and Debian.
Is there an exploit for CVE-2023-52621?
As of now, there are no known public exploits specifically targeting CVE-2023-52621.
What components of the Linux kernel are impacted by CVE-2023-52621?
CVE-2023-52621 impacts the BPF (Berkeley Packet Filter) functionality related to rcu_read_lock_trace_held() calls.