CVE-2026-53106

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-24. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

bpf: Do not allow deleting local storage in NMI

Currently, local storage may deadlock when deferring freeing selem or local storage through kfree_rcu(), call_rcu() or call_rcu_tasks_trace() in NMI or reentrant. Since deleting selem in NMI is an unlikely use case, partially mitigate it by returning error when calling from bpf_xxx_storage_delete() helpers in NMI. Note that, it is still possible to deadlock through reentrant. A full mitigation requires returning error when irqs_disabled() is true, which, however is too heavy-handed for bpf_xxx_storage_delete().

The long-term solution requires _nolock versions of call_rcu. Another possible solution is to defer the free through irq_work [0], but it would grow the size of selem, which is non-ideal.

The check is only needed in bpf_selem_unlink(), which is used by helpers and syscalls. bpf_selem_unlink_nofail() is fine as it is called during map and owner tear down that never run in NMI or reentrant.

[0] https://lore.kernel.org/bpf/[email protected]/

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 23, 2026

Advisory Details (2)

Auto-updated Jul 24, 2026
No patch confirmed yet.
generic

bpf: Do not allow deleting local storage in NMI - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: Do not allow deleting local storage in NMI - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/350de5b8a9befaa2a68861c51f671d4f5f751ca5

Vendor Advisories for CVE-2026-53106(2)

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

Patch Availability(5)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(5)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 15× in last 7d / 53× 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-29 00:48 UTCEG score recompute
  2. 2026-07-29 00:48 UTCGHSA enrichment
  3. 2026-07-28 15:37 UTCEPSS rescore
  4. 2026-07-27 17:34 UTCEG score recompute
  5. 2026-07-27 17:34 UTCGHSA enrichment
  6. 2026-07-26 15:27 UTCEG score recompute
  7. 2026-07-26 15:27 UTCVendor advisory
  8. 2026-07-26 15:27 UTCGHSA enrichment
  9. 2026-07-24 14:18 UTCEPSS rescore
  10. 2026-07-23 22:13 UTCEG score recompute 5.50
  11. 2026-07-23 22:13 UTCGHSA enrichment
  12. 2026-07-23 22:11 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  13. 2026-07-23 14:18 UTCEPSS rescore
  14. 2026-07-23 03:19 UTCEG score recompute
  15. 2026-07-22 14:08 UTCEPSS rescore
  16. 2026-07-21 15:25 UTCEPSS rescore
  17. 2026-07-20 17:08 UTCEPSS rescore
  18. 2026-07-19 14:31 UTCEPSS rescore
  19. 2026-07-19 14:31 UTCEPSS rescore
  20. 2026-07-19 02:29 UTCEPSS rescore
  21. 2026-07-18 10:04 UTCEPSS rescore
  22. 2026-07-17 00:18 UTCGHSA enrichment
  23. 2026-07-16 17:03 UTCEPSS rescore
  24. 2026-07-15 16:57 UTCEPSS rescore
  25. 2026-07-15 16:57 UTCEPSS rescore
Show 36 more
  1. 2026-07-15 02:00 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-13 22:31 UTCEPSS rescore
  4. 2026-07-13 20:04 UTCGHSA enrichment
  5. 2026-07-13 06:13 UTCEPSS rescore
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-12 05:46 UTCEPSS rescore
  8. 2026-07-11 08:27 UTCEPSS rescore
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-10 15:48 UTCGHSA enrichment
  11. 2026-07-09 19:10 UTCEPSS rescore
  12. 2026-07-09 19:10 UTCEPSS rescore
  13. 2026-07-08 15:16 UTCEPSS rescore
  14. 2026-07-08 15:16 UTCEPSS rescore
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-07 11:33 UTCGHSA enrichment
  18. 2026-07-06 02:23 UTCEPSS rescore
  19. 2026-07-06 02:23 UTCEPSS rescore
  20. 2026-07-05 02:31 UTCEPSS rescore
  21. 2026-07-05 02:30 UTCEPSS rescore
  22. 2026-07-04 07:18 UTCGHSA enrichment
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-01 15:07 UTCEPSS rescore
  25. 2026-07-01 02:40 UTCGHSA enrichment
  26. 2026-06-30 23:22 UTCEPSS rescore
  27. 2026-06-29 14:06 UTCEPSS rescore
  28. 2026-06-29 14:06 UTCEPSS rescore
  29. 2026-06-28 14:07 UTCEPSS rescore
  30. 2026-06-28 04:56 UTCEPSS rescore
  31. 2026-06-28 04:56 UTCEPSS rescore
  32. 2026-06-27 22:25 UTCGHSA enrichment
  33. 2026-06-27 03:08 UTCEPSS rescore
  34. 2026-06-25 13:49 UTCEPSS rescore
  35. 2026-06-24 18:10 UTCEG score recompute
  36. 2026-06-24 18:03 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-53106?
CVE-2026-53106 is a medium vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: bpf: Do not allow deleting local storage in NMI Currently, local storage may deadlock when deferring freeing selem or local storage through kfreercu(), callrcu() or callrcutasks_trace() in NMI or reentrant. Since deleting selem in…
When was CVE-2026-53106 disclosed?
CVE-2026-53106 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53106 actively exploited?
CVE-2026-53106 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.0% of all scored CVEs.
What is the CVSS score of CVE-2026-53106?
CVE-2026-53106 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53106?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53106, 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-53106

Explore →

Is Your Infrastructure Affected by CVE-2026-53106?

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