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
9%
KEV
Not listed

Published

June 24, 2026

Last Modified

August 19, 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(8)

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (499 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (337 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.12.96-1 (32 versions)6.12.101-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.10-1

Weakness Classification(1)

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

All Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 38× in last 7d / 158× 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 242 total refreshes for this CVE.

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

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 August 19, 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 91.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

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