CVE-2026-45933

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
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

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: Preserve id of register in sync_linked_regs()

sync_linked_regs() copies the id of known_reg to reg when propagating bounds of known_reg to reg using the off of known_reg, but when known_reg was linked to reg like:

known_reg = reg ; both known_reg and reg get same id known_reg += 4 ; known_reg gets off = 4, and its id gets BPF_ADD_CONST

now when a call to sync_linked_regs() happens, let's say with the following:

if known_reg >= 10 goto pc+2

known_reg's new bounds are propagated to reg but now reg gets BPF_ADD_CONST from the copy.

This means if another link to reg is created like:

another_reg = reg ; another_reg should get the id of reg but assign_scalar_id_before_mov() sees BPF_ADD_CONST on reg and assigns a new id to it.

As reg has a new id now, known_reg's link to reg is broken. If we find new bounds for known_reg, they will not be propagated to reg.

This can be seen in the selftest added in the next commit:

0: (85) call bpf_get_prandom_u32#7 ; R0=scalar() 1: (57) r0 &= 255 ; R0=scalar(smin=smin32=0,smax=umax=smax32=umax32=255,var_off=(0x0; 0xff)) 2: (bf) r1 = r0 ; R0=scalar(id=1,smin=smin32=0,smax=umax=smax32=umax32=255,var_off=(0x0; 0xff)) R1=scalar(id=1,smin=smin32=0,smax=umax=smax32=umax32=255,var_off=(0x0; 0xff)) 3: (07) r1 += 4 ; R1=scalar(id=1+4,smin=umin=smin32=umin32=4,smax=umax=smax32=umax32=259,var_off=(0x0; 0x1ff)) 4: (a5) if r1 < 0xa goto pc+4 ; R1=scalar(id=1+4,smin=umin=smin32=umin32=10,smax=umax=smax32=umax32=259,var_off=(0x0; 0x1ff)) 5: (bf) r2 = r0 ; R0=scalar(id=2,smin=umin=smin32=umin32=6,smax=umax=smax32=umax32=255) R2=scalar(id=2,smin=umin=smin32=umin32=6,smax=umax=smax32=umax32=255) 6: (a5) if r1 < 0xe goto pc+2 ; R1=scalar(id=1+4,smin=umin=smin32=umin32=14,smax=umax=smax32=umax32=259,var_off=(0x0; 0x1ff)) 7: (35) if r0 >= 0xa goto pc+1 ; R0=scalar(id=2,smin=umin=smin32=umin32=6,smax=umax=smax32=umax32=9,var_off=(0x0; 0xf)) 8: (37) r0 /= 0 div by zero

When 4 is verified, r1's bounds are propagated to r0 but r0 also gets BPF_ADD_CONST (bug). When 5 is verified, r0 gets a new id (2) and its link with r1 is broken.

After 6 we know r1 has bounds [14, 259] and therefore r0 should have bounds [10, 255], therefore the branch at 7 is always taken. But because r0's id was changed to 2, r1's new bounds are not propagated to r0. The verifier still thinks r0 has bounds [6, 255] before 7 and execution can reach div by zero.

Fix this by preserving id in sync_linked_regs() like off and subreg_def.

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

Published

May 27, 2026

Last Modified

August 5, 2026

Advisory Details (4)

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

bpf: Preserve id of register in sync_linked_regs() - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: Preserve id of register in sync_linked_regs() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/92a8cb1806adefb263cf096eab6705705cf7eee1
generic

bpf: Preserve id of register in sync_linked_regs() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/65d114b5270b62aefb820ecd6c3b7caeea8f895d
generic

bpf: Preserve id of register in sync_linked_regs() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/58059335e46537de682db84984f7716c813208c4

Vendor Advisories for CVE-2026-45933(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.12.75—osv

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 rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (103 versions)6.18.14-1—

Data Freshness Timeline

(refreshed 9× 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 236 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-45933?
CVE-2026-45933 is a high vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: bpf: Preserve id of register in synclinkedregs() synclinkedregs() copies the id of known_reg to reg when propagating bounds of knownreg to reg using the off of knownreg, but when known_reg was linked to reg like: knownreg = reg ;…
When was CVE-2026-45933 disclosed?
CVE-2026-45933 was first published in the National Vulnerability Database on May 27, 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-45933 actively exploited?
CVE-2026-45933 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 92.5% of all scored CVEs.
What is the CVSS score of CVE-2026-45933?
CVE-2026-45933 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-45933?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45933, 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-45933

Explore →

Is Your Infrastructure Affected by CVE-2026-45933?

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

Start Free Scan →Browse All CVEs