CVE-2026-45993

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: 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:

LoongArch: Add spectre boundry for syscall dispatch table

The LoongArch syscall number is directly controlled by userspace, but does not have a array_index_nospec() boundry to prevent access past the syscall function pointer tables.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 19, 2026

Advisory Details (5)

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

LoongArch: Add spectre boundry for syscall dispatch table - kernel/git/stable/linux.git - Linux kernel stable tree

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

LoongArch: Add spectre boundry for syscall dispatch table - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/85cbf7fb568af5358aae61925c4e66b8f5e1439d
generic

LoongArch: Add spectre boundry for syscall dispatch table - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/108f2cd13577a410c0ad6ea00708596d9d0dfc90
generic

LoongArch: Add spectre boundry for syscall dispatch table - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0c965d2784fbbd7f8e3b96d875c9cfdf7c00da3d
generic

LoongArch: Add spectre boundry for syscall dispatch table - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/07040904ad217545be096d4280ed33c02f6a3750

Vendor Advisories for CVE-2026-45993(2)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (335 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.86-1~bpo12+1 (19 versions)6.12.86-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.4-1~bpo13+1 (131 versions)7.0.4-1

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-45993?
CVE-2026-45993 is a medium vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: LoongArch: Add spectre boundry for syscall dispatch table The LoongArch syscall number is directly controlled by userspace, but does not have a arrayindexnospec() boundry to prevent access past the syscall function pointer tables.
When was CVE-2026-45993 disclosed?
CVE-2026-45993 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 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-45993 actively exploited?
CVE-2026-45993 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 96.2% of all scored CVEs.
What is the CVSS score of CVE-2026-45993?
CVE-2026-45993 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-45993?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45993, 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-45993

Explore →

Is Your Infrastructure Affected by CVE-2026-45993?

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