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.
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.
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.
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.