CVE-2026-53081

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
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.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

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.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

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%
EPSS PROB
0.2%
EPSS %ILE
7th
KEV
Not listed

Published

June 24, 2026

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated Jun 28, 2026
Patch available.
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(10)

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)
  • every version up to 6.12.94-1: fixed in 6.12.94-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)
  • every version up to 7.0.10-1: fixed in 7.0.10-1
—

Weakness Classification(1)

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

All Vendor Advisories

(10)

Data Freshness Timeline

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

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

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 on June 24, 2026, with the most recent update on August 5, 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.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53081?
CVE-2026-53081 has a CVSS base score of 7.8 (the CNA's own assessment, by linux; NVD's own analysis pending).
How do I remediate CVE-2026-53081?
A fix for CVE-2026-53081 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53081 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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