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
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(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-30ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16~24.04.1) @ noble2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu

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.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1—

Weakness Classification(1)

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

All Vendor Advisories

(8)

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 4× in last 7d / 59× 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.

Showing the most recent 100 of 171 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-04 05:06 UTCEPSS rescore
  6. 2026-09-01 04:40 UTCEPSS rescore
  7. 2026-08-30 19:53 UTCEG score recompute
  8. 2026-08-30 19:53 UTCVendor advisory
  9. 2026-08-30 19:53 UTCGHSA enrichment
  10. 2026-08-30 19:17 UTCEPSS rescore
  11. 2026-08-28 21:41 UTCEPSS rescore
  12. 2026-08-28 03:42 UTCEG score recompute
  13. 2026-08-28 03:42 UTCVendor advisory
  14. 2026-08-28 03:42 UTCGHSA enrichment
  15. 2026-08-27 14:25 UTCEPSS rescore
  16. 2026-08-26 14:46 UTCEPSS rescore
  17. 2026-08-25 13:49 UTCEPSS rescore
  18. 2026-08-24 13:20 UTCEG score recompute
  19. 2026-08-24 13:20 UTCVendor advisory
  20. 2026-08-24 13:20 UTCGHSA enrichment
  21. 2026-08-23 09:40 UTCEG score recompute
  22. 2026-08-23 09:40 UTCVendor advisory
  23. 2026-08-23 09:40 UTCGHSA enrichment
  24. 2026-08-23 00:19 UTCEPSS rescore
  25. 2026-08-22 11:31 UTCEG score recompute
Show 75 more
  1. 2026-08-22 11:31 UTCVendor advisory
  2. 2026-08-22 11:31 UTCGHSA enrichment
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-21 05:28 UTCEG score recompute
  5. 2026-08-21 05:28 UTCVendor advisory
  6. 2026-08-21 05:28 UTCGHSA enrichment
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-20 07:19 UTCEG score recompute
  9. 2026-08-20 07:19 UTCVendor advisory
  10. 2026-08-20 07:19 UTCGHSA enrichment
  11. 2026-08-19 17:04 UTCEPSS rescore
  12. 2026-08-19 02:03 UTCEG score recompute
  13. 2026-08-19 02:03 UTCVendor advisory
  14. 2026-08-19 02:03 UTCGHSA enrichment
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-16 20:07 UTCEG score recompute
  18. 2026-08-16 20:07 UTCVendor advisory
  19. 2026-08-16 20:07 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 21:19 UTCEG score recompute
  23. 2026-08-15 21:19 UTCVendor advisory
  24. 2026-08-15 21:19 UTCGHSA enrichment
  25. 2026-08-15 01:30 UTCEPSS rescore
  26. 2026-08-14 23:10 UTCVendor advisory
  27. 2026-08-14 23:10 UTCGHSA enrichment
  28. 2026-08-14 01:01 UTCEG score recompute
  29. 2026-08-14 01:01 UTCVendor advisory
  30. 2026-08-14 01:01 UTCGHSA enrichment
  31. 2026-08-13 22:00 UTCEPSS rescore
  32. 2026-08-13 02:52 UTCEG score recompute
  33. 2026-08-13 02:52 UTCVendor advisory
  34. 2026-08-13 02:52 UTCGHSA enrichment
  35. 2026-08-12 13:51 UTCEPSS rescore
  36. 2026-08-12 04:44 UTCEG score recompute
  37. 2026-08-12 04:44 UTCVendor advisory
  38. 2026-08-12 04:44 UTCGHSA enrichment
  39. 2026-08-11 06:36 UTCEG score recompute
  40. 2026-08-11 06:36 UTCVendor advisory
  41. 2026-08-11 06:36 UTCGHSA enrichment
  42. 2026-08-11 00:00 UTCEPSS rescore
  43. 2026-08-10 08:27 UTCEG score recompute
  44. 2026-08-10 08:27 UTCVendor advisory
  45. 2026-08-10 08:27 UTCGHSA enrichment
  46. 2026-08-09 13:46 UTCEPSS rescore
  47. 2026-08-09 10:19 UTCEG score recompute
  48. 2026-08-09 10:19 UTCVendor advisory
  49. 2026-08-09 10:19 UTCGHSA enrichment
  50. 2026-08-08 16:37 UTCEPSS rescore
  51. 2026-08-08 12:11 UTCEG score recompute
  52. 2026-08-08 12:11 UTCVendor advisory
  53. 2026-08-08 12:11 UTCGHSA enrichment
  54. 2026-08-07 14:02 UTCVendor advisory
  55. 2026-08-07 14:02 UTCGHSA enrichment
  56. 2026-08-06 15:53 UTCEG score recompute
  57. 2026-08-06 15:53 UTCVendor advisory
  58. 2026-08-06 15:53 UTCGHSA enrichment
  59. 2026-08-06 13:47 UTCEPSS rescore
  60. 2026-08-05 19:17 UTCEPSS rescore
  61. 2026-08-05 17:21 UTCEG score recompute
  62. 2026-08-05 17:21 UTCVendor advisory
  63. 2026-08-05 17:20 UTCGHSA enrichment
  64. 2026-08-04 15:10 UTCEPSS rescore
  65. 2026-08-04 15:10 UTCEG score recompute
  66. 2026-08-04 15:10 UTCVendor advisory
  67. 2026-08-04 15:10 UTCGHSA enrichment
  68. 2026-08-04 10:39 UTCEPSS rescore
  69. 2026-08-03 16:57 UTCEG score recompute
  70. 2026-08-03 16:57 UTCVendor advisory
  71. 2026-08-03 16:57 UTCGHSA enrichment
  72. 2026-08-03 10:36 UTCEPSS rescore
  73. 2026-08-02 18:48 UTCVendor advisory
  74. 2026-08-02 18:48 UTCGHSA enrichment
  75. 2026-08-01 20:39 UTCEG score recompute

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

See which npm, PyPI, Go, and Maven packages are affected by 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.

Start Free Scan →Browse All CVEs