CVE-2026-53092

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
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: Fix linked reg delta tracking when src_reg == dst_reg

Consider the case of rX += rX where src_reg and dst_reg are pointers to the same bpf_reg_state in adjust_reg_min_max_vals(). The latter first modifies the dst_reg in-place, and later in the delta tracking, the subsequent is_reg_const(src_reg)/reg_const_value(src_reg) reads the post-{add,sub} value instead of the original source.

This is problematic since it sets an incorrect delta, which sync_linked_regs() then propagates to linked registers, thus creating a verifier-vs-runtime mismatch. Fix it by just skipping this corner case.

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

Published

June 24, 2026

Last Modified

July 15, 2026

Advisory Details (3)

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

bpf: Fix linked reg delta tracking when src_reg == dst_reg - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: Fix linked reg delta tracking when src_reg == dst_reg - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: Fix linked reg delta tracking when src_reg == dst_reg - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cc86a8b0a1c54d2bccf6f68cf49b82dea91b84de

Vendor Advisories for CVE-2026-53092(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 73× 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-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-17 01:06 UTCGHSA enrichment
  8. 2026-07-16 17:03 UTCEPSS rescore
  9. 2026-07-16 12:43 UTCGHSA enrichment
  10. 2026-07-16 00:21 UTCGHSA enrichment
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 11:58 UTCGHSA enrichment
  14. 2026-07-15 02:00 UTCEPSS rescore
  15. 2026-07-15 02:00 UTCEPSS rescore
  16. 2026-07-14 22:53 UTCGHSA enrichment
  17. 2026-07-14 10:30 UTCGHSA enrichment
  18. 2026-07-13 22:31 UTCEPSS rescore
  19. 2026-07-13 22:05 UTCGHSA enrichment
  20. 2026-07-13 09:41 UTCGHSA enrichment
  21. 2026-07-13 06:13 UTCEPSS rescore
  22. 2026-07-13 06:13 UTCEPSS rescore
  23. 2026-07-12 21:19 UTCGHSA enrichment
  24. 2026-07-12 08:36 UTCGHSA enrichment
  25. 2026-07-12 05:46 UTCEPSS rescore
Show 48 more
  1. 2026-07-11 20:14 UTCGHSA enrichment
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-11 07:52 UTCGHSA enrichment
  5. 2026-07-10 19:30 UTCGHSA enrichment
  6. 2026-07-10 07:08 UTCGHSA enrichment
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-09 18:39 UTCGHSA enrichment
  10. 2026-07-09 06:17 UTCGHSA enrichment
  11. 2026-07-08 17:54 UTCGHSA enrichment
  12. 2026-07-08 15:16 UTCEPSS rescore
  13. 2026-07-08 15:16 UTCEPSS rescore
  14. 2026-07-08 05:27 UTCGHSA enrichment
  15. 2026-07-07 16:54 UTCGHSA enrichment
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-07 03:30 UTCGHSA enrichment
  19. 2026-07-06 16:27 UTCEPSS rescore
  20. 2026-07-06 16:27 UTCEPSS rescore
  21. 2026-07-06 15:08 UTCGHSA enrichment
  22. 2026-07-06 02:44 UTCGHSA enrichment
  23. 2026-07-05 14:20 UTCGHSA enrichment
  24. 2026-07-05 02:31 UTCEPSS rescore
  25. 2026-07-05 02:30 UTCEPSS rescore
  26. 2026-07-05 01:58 UTCGHSA enrichment
  27. 2026-07-04 13:36 UTCGHSA enrichment
  28. 2026-07-04 06:31 UTCEPSS rescore
  29. 2026-07-04 01:12 UTCGHSA enrichment
  30. 2026-07-03 12:49 UTCGHSA enrichment
  31. 2026-07-03 00:19 UTCGHSA enrichment
  32. 2026-07-02 11:56 UTCGHSA enrichment
  33. 2026-07-01 23:34 UTCGHSA enrichment
  34. 2026-07-01 11:11 UTCGHSA enrichment
  35. 2026-06-30 23:22 UTCEPSS rescore
  36. 2026-06-30 22:49 UTCEG score recompute 7.80
  37. 2026-06-30 22:49 UTCGHSA enrichment
  38. 2026-06-29 14:06 UTCEPSS rescore
  39. 2026-06-29 14:06 UTCEPSS rescore
  40. 2026-06-28 14:07 UTCEPSS rescore
  41. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  42. 2026-06-28 04:56 UTCEPSS rescore
  43. 2026-06-28 04:56 UTCEPSS rescore
  44. 2026-06-27 20:29 UTCGHSA enrichment
  45. 2026-06-27 03:08 UTCEPSS rescore
  46. 2026-06-25 13:49 UTCEPSS rescore
  47. 2026-06-24 18:12 UTCEG score recompute
  48. 2026-06-24 18:03 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-53092?
CVE-2026-53092 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: bpf: Fix linked reg delta tracking when srcreg == dstreg Consider the case of rX += rX where srcreg and dstreg are pointers to the same bpfregstate in adjustregminmaxvals(). The latter first modifies the dst_reg in-place, and later…
When was CVE-2026-53092 disclosed?
CVE-2026-53092 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53092 actively exploited?
CVE-2026-53092 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53092?
CVE-2026-53092 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53092?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53092, 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-53092

Explore →

Is Your Infrastructure Affected by CVE-2026-53092?

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