LiveActive security incident?Get immediate response
CVE Record

CVE-2026-45993: LoongArch: Add spectre boundry for syscall dispatch table

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2026-45993 is a Linux kernel issue specific to LoongArch syscall handling. User-controlled syscall numbers lacked a Spectre-style bounds barrier before indexing syscall function pointer tables, creating a potential speculative out-of-bounds access risk. No CVSS score, CWE, or exploitation evidence is provided.

Executive priority

Moderate tracking priority if the organization uses LoongArch Linux; otherwise likely low operational relevance. Because severity and exploitation evidence are incomplete, focus on asset confirmation and normal kernel patch governance rather than emergency response.

Technical view

The LoongArch syscall dispatch path used a userspace-controlled syscall number without an array_index_nospec() boundary before table lookup. The upstream fix adds a Spectre mitigation boundary around syscall table indexing. The source bundle lists Linux kernel versions as affected but provides no distro mapping or CPEs.

Likely exposure

Exposure appears limited to systems running Linux on the LoongArch architecture with affected kernel builds. The bundle does not identify affected distributions, products, cloud images, or CPEs, so organizations must map upstream kernel status to their vendor kernels.

Exploitation context

The CVE is not listed as KEV in the provided bundle. The sources do not state active exploitation, public exploit availability, or confirmed real-world attacks. Treat this as a speculative-execution hardening issue until vendor advisories provide more impact detail.

Researcher notes

Key unknowns are practical impact, data exposure scope, and distribution backport status. The CVE describes a missing Spectre boundary, not a conventional memory-corruption primitive. Avoid assuming exploitability beyond the provided kernel description.

Mitigation direction

  • Identify Linux systems running on LoongArch architecture.
  • Check kernel vendor advisories for CVE-2026-45993 backports or fixed packages.
  • Update affected kernels when vendor-supported fixes are available.
  • Prioritize internet-facing or multi-tenant LoongArch systems if present.
  • Use kernel stable commits only as vendor-mapping evidence, not standalone deployment guidance.

Validation and detection

  • Inventory LoongArch hosts and record running kernel versions.
  • Map distro kernel packages to the upstream fixed stable commits.
  • Confirm patched source includes array_index_nospec() protection in LoongArch syscall dispatch.
  • Review vendor changelogs for CVE-2026-45993 or equivalent backport references.
  • Document systems where no LoongArch Linux exposure exists.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-45993 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
6Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxbe769645a2aef577f07afdcb4de8fad20b6d57c0, be769645a2aef577f07afdcb4de8fad20b6d57c0, be769645a2aef577f07afdcb4de8fad20b6d57c0, be769645a2aef577f07afdcb4de8fad20b6d57c0, be769645a2aef577f07afdcb4de8fad20b6d57c0unaffected
LinuxLinux5.19, 0, 6.6.140, 6.12.86, 6.18.27, 7.0.4, 7.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.