Answer in brief
CVE-2026-43351 records a Unknown severity vulnerability in KVM: arm64: Eagerly init vgic dist/redist on vgic 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 | >=b3aa9283c0c505b5cfd25f7d6cfd720de2adc807 <b7493f48c3dba75674a4ee505b4afa8fe5102457 || >=b3aa9283c0c505b5cfd25f7d6cfd720de2adc807 <a24f1d80fbcdbf8b2a7044a00fa12b3972b4c31c || >=b3aa9283c0c505b5cfd25f7d6cfd720de2adc807 <ac6769c8f948dff33265c50e524aebf9aa6f1be0 | b7493f48c3dba75674a4ee505b4afa8fe5102457, a24f1d80fbcdbf8b2a7044a00fa12b3972b4c31c, ac6769c8f948dff33265c50e524aebf9aa6f1be0 |
| Linux/Linuxgeneric | 6.14 | Not reported |
Published upstream
May 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 6, 2026
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Eagerly init vgic dist/redist on vgic creation If vgic_allocate_private_irqs_locked() fails for any odd reason, we exit kvm_vgic_create() early, leaving dist->rd_regions uninitialised. kvm_vgic_dist_destroy() then comes along and walks into the weeds trying to free the RDs. Got to love this stuff. Solve it by moving all the static initialisation early, and make sure that if we fail halfway, we're in a reasonable shape to perform the rest of the teardown. While at it, reset the vgic model on failure, just in case...
Quoted source text, attributed separately from HOL analysis.