CVE-2023-52621: bpf: Check rcu_read_lock_trace_held() before calling bpf map helpers
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 169410eba271afc9f0fb476d996795aa26770c6d, 3516f93cc63d956e1b290ae4b7bf2586074535a0, 483cb92334cd7f1d5387dccc0ab5d595d27a669d.
Low priority for now. Upgrade to Linux Linux 169410eba271afc9f0fb476d996795aa26770c6d, 3516f93cc63d956e1b290ae4b7bf2586074535a0, 483cb92334cd7f1d5387dccc0ab5d595d27a669d or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: bpf: Check rcu_read_lock_trace_held() before calling bpf map helpers These three bpf_map_{lookup,update,delete}_elem() helpers are also available for sleepable bpf program, so add the corresponding lock assertion for sleepable bpf program, otherwise the following warning will be reported when a sleepable bpf program manipulates bpf map under interpreter mode (aka bpf_jit_enable=0): WARNING: CPU: 3 PID: 4985 at kernel/bpf/helpers.c:40 ...... CPU: 3 PID: 4985 Comm: test_progs Not tainted 6.6.0+ #2 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) ...... RIP: 0010:bpf_map_lookup_elem+0x54/0x60 ...... Call Trace: <TASK> ? __warn+0xa5/0x240 ? bpf_map_lookup_elem+0x54/0x60 ? report_bug+0x1ba/0x1f0 ? handle_bug+0x40/0x80 ? exc_invalid_op+0x18/0x50 ? asm_exc_invalid_op+0x1b/0x20 ? __pfx_bpf_map_lookup_elem+0x10/0x10 ? rcu_lockdep_current_cpu_online+0x65/0xb0 ? rcu_is_watching+0x23/0x50 ? bpf_map_lookup_elem+0x54/0x60 ? __pfx_bpf_map_lookup_elem+0x10/0x10 ___bpf_prog_run+0x513/0x3b70 __bpf_prog_run32+0x9d/0xd0 ? __bpf_prog_enter_sleepable_recur+0xad/0x120 ? __bpf_prog_enter_sleepable_recur+0x3e/0x120 bpf_trampoline_6442580665+0x4d/0x1000 __x64_sys_getpgid+0x5/0x30 ? do_syscall_64+0x36/0xb0 entry_SYSCALL_64_after_hwframe+0x6e/0x76 </TASK>
- Published
- Mar 26, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-617
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.10affected
- 1e6c62a8821557720a9b2ea9617359b264f2f67c and later · before 82f2df94dac1aa9b879e74d1f82ba1b631bdc612affected · git
- 1e6c62a8821557720a9b2ea9617359b264f2f67c and later · before 3516f93cc63d956e1b290ae4b7bf2586074535a0affected · git
- 1e6c62a8821557720a9b2ea9617359b264f2f67c and later · before d6d6fe4bb105595118f12abeed4a7bdd450853f3affected · git
- 1e6c62a8821557720a9b2ea9617359b264f2f67c and later · before 483cb92334cd7f1d5387dccc0ab5d595d27a669daffected · git
- 1e6c62a8821557720a9b2ea9617359b264f2f67c and later · before c7f1b6146f4a46d727c0d046284c28b6882c6304affected · git
- 1e6c62a8821557720a9b2ea9617359b264f2f67c and later · before 169410eba271afc9f0fb476d996795aa26770c6daffected · git
- before 5.10not affected · semver
- 5.10.237 and later · up to and including 5.10.*not affected · semver
- 5.15.181 and later · up to and including 5.15.*not affected · semver
Affected versions · NVD (6)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel5.10 and later · before 5.10.237
- linux linux kernel5.11 and later · before 5.15.181
- linux linux kernel5.16 and later · before 6.1.77
- linux linux kernel6.2 and later · before 6.6.16
- linux linux kernel6.7 and later · before 6.7.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | linux | before 5.10.237-1 | 5.10.237-1 |
| Debian:12 | linux | before 6.1.82-1 | 6.1.82-1 |
| Debian:13 | linux | before 6.7.7-1 | 6.7.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2021-47180Mar 25, 2024 · NFC: nci: fix memory leak in nci_allocate_device22Monitor
- ← EarlierCVE-2024-26644Mar 26, 2024 · btrfs: don't abort filesystem when attempting to snapshot deleted subvolume22Monitor
- Later →CVE-2023-52623Mar 26, 2024 · SUNRPC: Fix a suspicious RCU usage warning22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 169410eba271afc9f0fb476d996795aa26770c6d | Vendor (CNA) |
| Linux Linux | 3516f93cc63d956e1b290ae4b7bf2586074535a0 | Vendor (CNA) |
| Linux Linux | 483cb92334cd7f1d5387dccc0ab5d595d27a669d | Vendor (CNA) |
| Linux Linux | 82f2df94dac1aa9b879e74d1f82ba1b631bdc612 | Vendor (CNA) |
| Linux Linux | c7f1b6146f4a46d727c0d046284c28b6882c6304 | Vendor (CNA) |
| Linux Linux | d6d6fe4bb105595118f12abeed4a7bdd450853f3 | Vendor (CNA) |
| debian:linux | 6.1.82-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2023-2156322 days apartA flaw was found in the networking subsystem of the Linux kernel within the handling of the RPL protocol.32Monitor
- CVE-2025-39803538 days apartscsi: ufs: core: Remove WARN_ON_ONCE() call from ufshcd_uic_cmd_compl()31Monitor
- CVE-2024-267268 days apartbtrfs: don't drop extent_map for free space inode on write error22Monitor
- CVE-2024-267278 days apartbtrfs: do not ASSERT() if the newly created subvolume already got read22Monitor
- CVE-2023-5256924 days apartbtrfs: remove BUG() after failure to insert delayed dir index item22Monitor
- CVE-2022-4863333 days apartdrm/gma500: Fix WARN_ON(lock->magic != lock) error22Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-617 · Reachable AssertionCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/3516f93cc63d956e1b290ae4b7bf2586074535a0
- git.kernel.org/stable/c/483cb92334cd7f1d5387dccc0ab5d595d27a669d
- git.kernel.org/stable/c/82f2df94dac1aa9b879e74d1f82ba1b631bdc612
- git.kernel.org/stable/c/c7f1b6146f4a46d727c0d046284c28b6882c6304
- git.kernel.org/stable/c/d6d6fe4bb105595118f12abeed4a7bdd450853f3
- lists.debian.org/debian-lts-announce/2025/05/msg00030.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.