Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-52621: bpf: Check rcu_read_lock_trace_held() before calling bpf map helpers

HighCVSS 7.8 · v3.1—No exploit Fix available

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

Report tools

JSON

Action score

31

Monitor

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.

Follow CVE-2023-52621

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
linuxlinux kernel
debiandebian 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

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:11linuxbefore 5.10.237-15.10.237-1
Debian:12linuxbefore 6.1.82-16.1.82-1
Debian:13linuxbefore 6.7.7-16.7.7-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2021-47180Mar 25, 2024 · NFC: nci: fix memory leak in nci_allocate_device
    22Monitor
  • ← EarlierCVE-2024-26644Mar 26, 2024 · btrfs: don't abort filesystem when attempting to snapshot deleted subvolume
    22Monitor
  • Later →CVE-2023-52623Mar 26, 2024 · SUNRPC: Fix a suspicious RCU usage warning
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux169410eba271afc9f0fb476d996795aa26770c6dVendor (CNA)
Linux Linux3516f93cc63d956e1b290ae4b7bf2586074535a0Vendor (CNA)
Linux Linux483cb92334cd7f1d5387dccc0ab5d595d27a669dVendor (CNA)
Linux Linux82f2df94dac1aa9b879e74d1f82ba1b631bdc612Vendor (CNA)
Linux Linuxc7f1b6146f4a46d727c0d046284c28b6882c6304Vendor (CNA)
Linux Linuxd6d6fe4bb105595118f12abeed4a7bdd450853f3Vendor (CNA)
debian:linux6.1.82-1 · Debian:12Package 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 error
    22Monitor
  • CVE-2024-267278 days apartbtrfs: do not ASSERT() if the newly created subvolume already got read
    22Monitor
  • CVE-2023-5256924 days apartbtrfs: remove BUG() after failure to insert delayed dir index item
    22Monitor
  • CVE-2022-4863333 days apartdrm/gma500: Fix WARN_ON(lock->magic != lock) error
    22Monitor

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 Assertion

CVSS 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.

References

All records