Answer in brief
CVE-2025-37849 records a Unknown severity vulnerability in KVM: arm64: Tear down vGIC on failed vCPU creation. 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.
Answer in brief
CVE-2025-37849 records a Unknown severity vulnerability in KVM: arm64: Tear down vGIC on failed vCPU creation. 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 | >=6211753fdfd05af9e08f54c8d0ba3ee516034878 <07476e0d932afc53c05468076393ac35d0b4999e || >=6211753fdfd05af9e08f54c8d0ba3ee516034878 <5085e02362b9948f82fceca979b8f8e12acb1cc5 || >=6211753fdfd05af9e08f54c8d0ba3ee516034878 <c322789613407647a05ff5c451a7bf545fb34e73 || >=6211753fdfd05af9e08f54c8d0ba3ee516034878 <2480326eba8ae9ccc5e4c3c2dc8d407db68e3c52 || >=6211753fdfd05af9e08f54c8d0ba3ee516034878 <f1e9087abaeedec9bf2894a282ee4f0d8383f299 || >=6211753fdfd05af9e08f54c8d0ba3ee516034878 <250f25367b58d8c65a1b060a2dda037eea09a672 | 07476e0d932afc53c05468076393ac35d0b4999e, 5085e02362b9948f82fceca979b8f8e12acb1cc5, c322789613407647a05ff5c451a7bf545fb34e73, 2480326eba8ae9ccc5e4c3c2dc8d407db68e3c52, f1e9087abaeedec9bf2894a282ee4f0d8383f299, 250f25367b58d8c65a1b060a2dda037eea09a672 |
| Linux/Linuxgeneric | 3.11 | Not reported |
Published upstream
May 9, 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: KVM: arm64: Tear down vGIC on failed vCPU creation If kvm_arch_vcpu_create() fails to share the vCPU page with the hypervisor, we propagate the error back to the ioctl but leave the vGIC vCPU data initialised. Note only does this leak the corresponding memory when the vCPU is destroyed but it can also lead to use-after-free if the redistributor device handling tries to walk into the vCPU. Add the missing cleanup to kvm_arch_vcpu_create(), ensuring that the vGIC vCPU structures are destroyed on error.
Quoted source text, attributed separately from HOL analysis.
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 | >=6211753fdfd05af9e08f54c8d0ba3ee516034878 <07476e0d932afc53c05468076393ac35d0b4999e || >=6211753fdfd05af9e08f54c8d0ba3ee516034878 <5085e02362b9948f82fceca979b8f8e12acb1cc5 || >=6211753fdfd05af9e08f54c8d0ba3ee516034878 <c322789613407647a05ff5c451a7bf545fb34e73 || >=6211753fdfd05af9e08f54c8d0ba3ee516034878 <2480326eba8ae9ccc5e4c3c2dc8d407db68e3c52 || >=6211753fdfd05af9e08f54c8d0ba3ee516034878 <f1e9087abaeedec9bf2894a282ee4f0d8383f299 || >=6211753fdfd05af9e08f54c8d0ba3ee516034878 <250f25367b58d8c65a1b060a2dda037eea09a672 | 07476e0d932afc53c05468076393ac35d0b4999e, 5085e02362b9948f82fceca979b8f8e12acb1cc5, c322789613407647a05ff5c451a7bf545fb34e73, 2480326eba8ae9ccc5e4c3c2dc8d407db68e3c52, f1e9087abaeedec9bf2894a282ee4f0d8383f299, 250f25367b58d8c65a1b060a2dda037eea09a672 |
| Linux/Linuxgeneric | 3.11 | Not reported |
Published upstream
May 9, 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: KVM: arm64: Tear down vGIC on failed vCPU creation If kvm_arch_vcpu_create() fails to share the vCPU page with the hypervisor, we propagate the error back to the ioctl but leave the vGIC vCPU data initialised. Note only does this leak the corresponding memory when the vCPU is destroyed but it can also lead to use-after-free if the redistributor device handling tries to walk into the vCPU. Add the missing cleanup to kvm_arch_vcpu_create(), ensuring that the vGIC vCPU structures are destroyed on error.
Quoted source text, attributed separately from HOL analysis.