CVE-2026-45933

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 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
7%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 24, 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.

Data Freshness Timeline

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

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

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 June 24, 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 v3 base score of 7.8 (NVD).
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

Explore the affected products and dependency analysis for 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