CVE-2026-53081

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: Enforce regsafe base id consistency for BPF_ADD_CONST scalars

When regsafe() compares two scalar registers that both carry BPF_ADD_CONST, check_scalar_ids() maps their full compound id (aka base | BPF_ADD_CONST flag) as one idmap entry. However, it never verifies that the underlying base ids, that is, with the flag stripped are consistent with existing idmap mappings.

This allows construction of two verifier states where the old state has R3 = R2 + 10 (both sharing base id A) while the current state has R3 = R4 + 10 (base id C, unrelated to R2). The idmap creates two independent entries: A->B (for R2) and A|flag->C|flag (for R3), without catching that A->C conflicts with A->B. State pruning then incorrectly succeeds.

Fix this by additionally verifying base ID mapping consistency whenever BPF_ADD_CONST is set: after mapping the compound ids, also invoke check_ids() on the base IDs (flag bits stripped). This ensures that if A was already mapped to B from comparing the source register, any ADD_CONST derivative must also derive from B, not an unrelated C.

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

Published

June 24, 2026

Last Modified

July 23, 2026

Advisory Details (4)

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

bpf: Enforce regsafe base id consistency for BPF_ADD_CONST scalars - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7d73c72cccac651acc891377a5e623e4021c6380
generic

bpf: Enforce regsafe base id consistency for BPF_ADD_CONST scalars - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/691adf738817275368ed56311b7d798d617823a3
generic

bpf: Enforce regsafe base id consistency for BPF_ADD_CONST scalars - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2f2ec8e7730e21fc9bd49e0de9cdd58213ea24d0
generic

bpf: Enforce regsafe base id consistency for BPF_ADD_CONST scalars - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/13c02881e49aac4c82b261faa26db9edf2567231

Vendor Advisories for CVE-2026-53081(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)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-07-27ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-07-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-07-27ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-07-27ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-07-27ubuntu

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

Frequently asked(5)

What is CVE-2026-53081?
CVE-2026-53081 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: bpf: Enforce regsafe base id consistency for BPFADDCONST scalars When regsafe() compares two scalar registers that both carry BPFADDCONST, checkscalarids() maps their full compound id (aka base | BPFADDCONST flag) as one idmap…
When was CVE-2026-53081 disclosed?
CVE-2026-53081 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-53081 actively exploited?
CVE-2026-53081 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.6% of all scored CVEs.
What is the CVSS score of CVE-2026-53081?
CVE-2026-53081 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53081?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53081, 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-53081

Explore →

Is Your Infrastructure Affected by CVE-2026-53081?

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

Start Free Scan →Browse All CVEs