LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38366: LoongArch: KVM: Check validity of "num_cpu" from user space

In the Linux kernel, the following vulnerability has been resolved: LoongArch: KVM: Check validity of "num_cpu" from user space The maximum supported cpu number is EIOINTC_ROUTE_MAX_VCPUS about irqchip EIOINTC, here add validation about cpu number to avoid array pointer overflow.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A local, low-privileged user may supply an invalid virtual CPU count to KVM on affected LoongArch systems, causing an array pointer overflow in the EIOINTC interrupt controller. The supplied CVSS assessment indicates possible loss of confidentiality, integrity, and availability, but the sources do not describe demonstrated impact.

Executive priority

Treat as high priority where affected LoongArch KVM hosts exist, especially in multi-tenant environments. Schedule prompt patching after vendor confirmation. Organizations without LoongArch KVM exposure can deprioritize after documenting that determination.

Technical view

LoongArch KVM did not validate user-controlled "num_cpu" against EIOINTC_ROUTE_MAX_VCPUS before using it in EIOINTC-related array handling. The kernel fix adds CPU-count validation to prevent array pointer overflow. The bundle identifies Linux kernel versions 6.13 through 6.15.5 as affected, with 6.16 appearing as a boundary, but exact range semantics are unclear.

Likely exposure

Exposure appears limited to affected Linux kernels on LoongArch systems using KVM and the EIOINTC irqchip. The CVSS vector requires local access and low privileges. Other architectures and LoongArch hosts not using this virtualization path are not shown as affected by the supplied evidence.

Exploitation context

The CVSS vector describes local, low-complexity exploitation requiring low privileges and no user interaction. The bundle marks the CVE as absent from KEV and provides no evidence of active exploitation, public proof-of-concept code, or successful guest-to-host escape.

Researcher notes

The source bundle establishes missing bounds validation and two stable-kernel fixes, but does not provide CWE classification, crash evidence, exploitability testing, or precise downstream package mappings. The duplicated commit-based version entry and ambiguous 6.16 boundary require confirmation against distribution advisories before declaring individual systems vulnerable.

Mitigation direction

  • Update to a vendor-supported kernel containing the cited upstream fix.
  • Check distribution advisories for corrected package versions and backports.
  • Restrict local and virtualization-management access until affected hosts are updated.
  • Prioritize internet-facing or multi-tenant LoongArch KVM hosts.

Validation and detection

  • Inventory LoongArch hosts running KVM and using the EIOINTC irqchip.
  • Record kernel versions and compare them with vendor advisories.
  • Confirm the vendor kernel includes either cited corrective commit or an equivalent backport.
  • After updating, verify the expected kernel is running on every affected host.
Prepared
Confidence
medium
Sources
4

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-2025-38366 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-38366Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1ad7efa552fd5cf4e8c49fea863c5c6a5dcf9f00, 1ad7efa552fd5cf4e8c49fea863c5c6a5dcf9f00unaffected
LinuxLinux6.13, 0, 6.15.5, 6.16affected
Weakness

CWE details

No CWE listed

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