Answer in brief
CVE-2025-38366 records a Unknown severity vulnerability in LoongArch: KVM: Check validity of "num_cpu" from user space. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1ad7efa552fd5cf4e8c49fea863c5c6a5dcf9f00 <a3293b4078ee93174f70f36d3ab7618554ce6ab6 || >=1ad7efa552fd5cf4e8c49fea863c5c6a5dcf9f00 <cc8d5b209e09d3b52bca1ffe00045876842d96ae | a3293b4078ee93174f70f36d3ab7618554ce6ab6, cc8d5b209e09d3b52bca1ffe00045876842d96ae |
| Linux/Linuxgeneric | 6.13 | Not reported |
Published upstream
Jul 25, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-38366 records a Unknown severity vulnerability in LoongArch: KVM: Check validity of "num_cpu" from user space. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1ad7efa552fd5cf4e8c49fea863c5c6a5dcf9f00 <a3293b4078ee93174f70f36d3ab7618554ce6ab6 || >=1ad7efa552fd5cf4e8c49fea863c5c6a5dcf9f00 <cc8d5b209e09d3b52bca1ffe00045876842d96ae | a3293b4078ee93174f70f36d3ab7618554ce6ab6, cc8d5b209e09d3b52bca1ffe00045876842d96ae |
| Linux/Linuxgeneric | 6.13 | Not reported |
Published upstream
Jul 25, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.