CVE-2026-53090

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM 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 — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

bpf: Fix ld_{abs,ind} failure path analysis in subprogs

Usage of ld_{abs,ind} instructions got extended into subprogs some time ago via commit 09b28d76eac4 ("bpf: Add abnormal return checks."). These are only allowed in subprograms when the latter are BTF annotated and have scalar return types.

The code generator in bpf_gen_ld_abs() has an abnormal exit path (r0=0 + exit) from legacy cBPF times. While the enforcement is on scalar return types, the verifier must also simulate the path of abnormal exit if the packet data load via ld_{abs,ind} failed.

This is currently not the case. Fix it by having the verifier simulate both success and failure paths, and extend it in similar ways as we do for tail calls. The success path (r0=unknown, continue to next insn) is pushed onto stack for later validation and the r0=0 and return to the caller is done on the fall-through side.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 23, 2026

Advisory Details (2)

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

bpf: Fix ld_{abs,ind} failure path analysis in subprogs - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: Fix ld_{abs,ind} failure path analysis in subprogs - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-53090(1)

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)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-53090?
CVE-2026-53090 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: bpf: Fix ld_{abs,ind} failure path analysis in subprogs Usage of ld_{abs,ind} instructions got extended into subprogs some time ago via commit 09b28d76eac4 ("bpf: Add abnormal return checks."). These are only allowed in subprograms…
When was CVE-2026-53090 disclosed?
CVE-2026-53090 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-53090 actively exploited?
CVE-2026-53090 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 97.0% of all scored CVEs.
What is the CVSS score of CVE-2026-53090?
CVE-2026-53090 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53090?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53090, 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-53090

Explore →

Is Your Infrastructure Affected by CVE-2026-53090?

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