dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53096

HIGH · 7.8 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 5.15.209 / 6.1.175 or later.
See remediation →
80/100
Remediation priority · High
Zero-click 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: Use RCU-safe iteration in dev_map_redirect_multi() SKB path The DEVMAP_HASH branch in dev_map_redirect_multi() uses hlist_for_each_entry_safe() to iterate hash buckets, but this function runs under RCU protection (called from xdp_do_generic_redirect_map() in softirq context). Concurrent writers (__dev_map_hash_update_elem, dev_map_hash_delete_elem) modify the list using RCU primitives (hlist_add_head_rcu, hlist_del_rcu). hlist_for_each_entry_safe() performs plain pointer dereferences without rcu_dereference(), missing the acquire barrier needed to pair with writers' rcu_assign_pointer(). On weakly-ordered architectures (ARM64, POWER), a reader can observe a partially-constructed node. It also defeats CONFIG_PROVE_RCU lockdep validation and KCSAN data-race detection. Replace with hlist_for_each_entry_rcu() using rcu_read_lock_bh_held() as the lockdep condition, consistent with the rcu_dereference_check() used in the DEVMAP (non-hash) branch of the same functions. Also fix the same incorrect lockdep_is_held(&dtab->index_lock) condition in dev_map_enqueue_multi(), where the lock is not held either.

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

In the Linux kernel BPF subsystem, the DEVMAP_HASH branch in dev_map_redirect_multi() incorrectly uses hlist_for_each_entry_safe() for RCU-protected hash bucket iteration instead of hlist_for_each_entry_rcu(). This missing rcu_dereference() breaks the acquire barrier pairing with writers' rcu_assign_pointer(), allowing readers on weakly-ordered architectures (ARM64, POWER) to observe partially-constructed nodes. The same incorrect lockdep condition exists in dev_map_enqueue_multi().

MitigationApply the kernel patch to replace hlist_for_each_entry_safe() with hlist_for_each_entry_rcu() using rcu_read_lock_bh_held() as the lockdep condition, and correct the lockdep_is_held() condition in dev_map_enqueue_multi(). Update to a kernel version containing this fix.

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.14, < 5.15.209>= 5.16, < 6.1.175>= 6.2, < 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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
    Run 'uname -r' to get the running kernel version, then compare it to the version where the fix was applied (the fix replaces hlist_for_each_entry_safe with hlist_for_each_entry_rcu in dev_map_redirect_multi)
    Affected if The kernel version is older than the fixed version and BPF with devmap is in use
  2. Verify BPF devmap support is enabled
    Check kernel configuration for CONFIG_BPF and CONFIG_BPF_DEVMAP, or check if /sys/kernel/debug/bpf/ is accessible and contains devmap entries
    Affected if BPF devmap support is compiled into the kernel and actively used
  3. Check for active devmap usage
    Inspect BPF maps via 'bpftool map show' or check /sys/fs/bpf/ for devmap-type maps that are attached to network interfaces
    Affected if Any devmap entries exist (the race condition triggers during concurrent dev_map_redirect_multi or dev_map_enqueue_multi operations)
  4. Identify system architecture
    Run 'uname -m' or check 'cat /proc/cpuinfo' to determine the CPU architecture
    Affected if The system runs on ARM64 (aarch64) or POWER (ppc64le/ppc64) architectures, which are weakly-ordered and vulnerable to the partially-constructed node issue

A system is affected if it runs a vulnerable kernel version on ARM64 or POWER architecture, has BPF devmap enabled, and has active devmap entries being used concurrently.

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.

From vendor data
Upgrade available Upgrade to 5.15.209 / 6.1.175 / 6.6.141 or later
Fixed in 5.15.2096.1.1756.6.141
Interim mitigation

Apply the kernel patch to replace hlist_for_each_entry_safe() with hlist_for_each_entry_rcu() using rcu_read_lock_bh_held() as the lockdep condition, and correct the lockdep_is_held() condition in dev_map_enqueue_multi(). Update to a kernel version containing this fix.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53096 — 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-53096 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