dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53083

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 6.6.141 / 6.12.91 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix RCU stall in bpf_fd_array_map_clear() Add a missing cond_resched() in bpf_fd_array_map_clear() loop. For PROG_ARRAY maps with many entries this loop calls prog_array_map_poke_run() per entry which can be expensive, and without yielding this can cause RCU stalls under load: rcu: Stack dump where RCU GP kthread last ran: CPU: 0 UID: 0 PID: 30932 Comm: kworker/0:2 Not tainted 6.14.0-13195-g967e8def1100 #2 PREEMPT(undef) Workqueue: events prog_array_map_clear_deferred RIP: 0010:write_comp_data+0x38/0x90 kernel/kcov.c:246 Call Trace: <TASK> prog_array_map_poke_run+0x77/0x380 kernel/bpf/arraymap.c:1096 __fd_array_map_delete_elem+0x197/0x310 kernel/bpf/arraymap.c:925 bpf_fd_array_map_clear kernel/bpf/arraymap.c:1000 [inline] prog_array_map_clear_deferred+0x119/0x1b0 kernel/bpf/arraymap.c:1141 process_one_work+0x898/0x19d0 kernel/workqueue.c:3238 process_scheduled_works kernel/workqueue.c:3319 [inline] worker_thread+0x770/0x10b0 kernel/workqueue.c:3400 kthread+0x465/0x880 kernel/kthread.c:464 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:153 ret_from_fork_asm+0x19/0x30 arch/x86/entry/entry_64.S:245 </TASK>

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an RCU (Read-Copy-Update) stall vulnerability in the Linux kernel's BPF subsystem. The bpf_fd_array_map_clear() function lacks a cond_resched() call in its loop, causing it to process many PROG_ARRAY map entries without yielding CPU time. Under load with maps containing many entries, this causes the prog_array_map_poke_run() function to run continuously without scheduling, leading to RCU stalls.

MitigationApply the kernel patch to add cond_resched() in the bpf_fd_array_map_clear() loop. This is a single-line fix that yields CPU time during bulk map clearing operations, preventing RCU stalls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 5.5, < 6.6.141>= 6.7, < 6.12.91>= 6.13, < 6.18.33>= 6.19, < 7.0.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check kernel version against affected ranges
    Run 'uname -r' or cat /proc/version to get the kernel version, then compare against: >= 5.5, < 6.6.141; >= 6.7, < 6.12.91; >= 6.13, < 6.18.33; >= 6.19, < 7.0.10
    Affected if Kernel version falls within any of the affected version ranges
  2. Verify BPF subsystem is enabled
    Check if BPF is available by running 'bpftool prog show' or looking for /sys/kernel/debug/bpf/ directory
    Affected if BPF subsystem is loaded and available on the system
  3. Identify PROG_ARRAY maps in use
    Run 'bpftool map show' to list all BPF maps and look for map type 'prog_array' entries with high entry counts
    Affected if PROG_ARRAY maps exist with many entries (particularly large counts that would cause prolonged clearing operations)
  4. Check for recent map clearing activity
    Monitor dmesg for RCU-related warnings or stalls, or trace bpf_fd_array_map_clear operations if under active development/debugging
    Affected if RCU stall warnings appear in kernel logs after BPF map operations

The system is affected if running a kernel version in the affected ranges AND BPF PROG_ARRAY maps with many entries are being used, with clearing operations triggering potential RCU stalls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.6.141 / 6.12.91 / 6.18.33 or later
Fixed in 6.6.1416.12.916.18.33
Vendor patch git.kernel.org →
Interim mitigation

Apply the kernel patch to add cond_resched() in the bpf_fd_array_map_clear() loop. This is a single-line fix that yields CPU time during bulk map clearing operations, preventing RCU stalls.

Recommended fix High confidence

6.6.141, 6.12.91, 6.18.33, or 7.0.10 depending on your current branch

  1. Upgrade the Linux kernel to one of the fixed releases: 6.6.141, 6.12.91, 6.18.33, or 7.0.10 (or later stable releases)
Caveat Kernel upgrades may require rebuilding out-of-tree modules; ensure driver compatibility with target kernel version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53083 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53083 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data