CVE-2026-53096

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.8
EG Score
7.8(high)
EPSS
3.1%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 28, 2026

Advisory Details (7)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

bpf: Use RCU-safe iteration in dev_map_redirect_multi() SKB path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d4c4bd231ebad70e6f30db429e9640bf378b2f52
generic

bpf: Use RCU-safe iteration in dev_map_redirect_multi() SKB path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cb2c1f3cf65b855548e1b8d55a08bfbaa5a0901a
generic

bpf: Use RCU-safe iteration in dev_map_redirect_multi() SKB path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b089aa6e94d7a08e74d076a0fe274842dc9feccc
generic

bpf: Use RCU-safe iteration in dev_map_redirect_multi() SKB path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8ed82f807bb09d2c8455aaa665f2c6cb17bc6a19
generic

bpf: Use RCU-safe iteration in dev_map_redirect_multi() SKB path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7027e705062482a8cea43a1c13ede3c35653966f
generic

bpf: Use RCU-safe iteration in dev_map_redirect_multi() SKB path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/571a05ea1baaccc0dc1e0d227b2cbc978b96d392
generic

bpf: Use RCU-safe iteration in dev_map_redirect_multi() SKB path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4a3d0fe30b907ff324b1b49756f7e713d67f3645

Vendor Advisories for CVE-2026-53096(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 28× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 20:10 UTCEG score recompute
  2. 2026-07-06 20:09 UTCGHSA enrichment
  3. 2026-07-06 08:06 UTCEG score recompute
  4. 2026-07-06 08:06 UTCGHSA enrichment
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 20:06 UTCEG score recompute
  8. 2026-07-05 20:06 UTCGHSA enrichment
  9. 2026-07-05 08:06 UTCEG score recompute
  10. 2026-07-05 08:05 UTCGHSA enrichment
  11. 2026-07-04 19:59 UTCEG score recompute
  12. 2026-07-04 19:59 UTCGHSA enrichment
  13. 2026-07-04 07:59 UTCEG score recompute
  14. 2026-07-04 07:59 UTCGHSA enrichment
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-03 19:59 UTCEG score recompute
  17. 2026-07-03 19:59 UTCGHSA enrichment
  18. 2026-07-03 07:59 UTCEG score recompute
  19. 2026-07-03 07:59 UTCGHSA enrichment
  20. 2026-07-02 19:58 UTCEG score recompute
  21. 2026-07-02 19:57 UTCGHSA enrichment
  22. 2026-07-02 07:57 UTCEG score recompute
  23. 2026-07-02 07:57 UTCGHSA enrichment
  24. 2026-07-01 19:57 UTCEG score recompute
  25. 2026-07-01 19:57 UTCGHSA enrichment
Show 15 more
  1. 2026-07-01 07:57 UTCEG score recompute 7.80
  2. 2026-07-01 07:57 UTCGHSA enrichment
  3. 2026-06-30 23:22 UTCEPSS rescore
  4. 2026-06-29 14:06 UTCEPSS rescore
  5. 2026-06-29 14:06 UTCEPSS rescore
  6. 2026-06-28 14:07 UTCEPSS rescore
  7. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  8. 2026-06-28 04:56 UTCEPSS rescore
  9. 2026-06-28 04:56 UTCEPSS rescore
  10. 2026-06-28 01:04 UTCEG score recompute
  11. 2026-06-28 01:04 UTCGHSA enrichment
  12. 2026-06-27 03:08 UTCEPSS rescore
  13. 2026-06-25 13:49 UTCEPSS rescore
  14. 2026-06-24 18:11 UTCEG score recompute
  15. 2026-06-24 18:03 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-53096?
CVE-2026-53096 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: bpf: Use RCU-safe iteration in devmapredirect_multi() SKB path The DEVMAPHASH branch in devmapredirectmulti() uses hlistforeachentrysafe() to iterate hash buckets, but this function runs under RCU protection (called from…
When was CVE-2026-53096 disclosed?
CVE-2026-53096 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53096 actively exploited?
CVE-2026-53096 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53096?
CVE-2026-53096 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53096?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53096, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53096

Explore →

Is Your Infrastructure Affected by CVE-2026-53096?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.