Answer in brief
CVE-2026-46032 records a Unknown severity vulnerability in KVM: nSVM: Triple fault if restore host CR3 fails on nested #VMEXIT. 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 | 5.9 | Not reported |
| Linux/Linuxgeneric | >=d82aaef9c88aa27bce63751d6d6329920b1fe8da <b0eb0a8959ac2b808eb11548d002fe1f9b5650cc || >=d82aaef9c88aa27bce63751d6d6329920b1fe8da <9a738cf170a4a2332ea3a15e23ec65b5757fe4a1 || >=d82aaef9c88aa27bce63751d6d6329920b1fe8da <5d291ef0585ed880ed4dd71ea1a5965e0a65fb53 | b0eb0a8959ac2b808eb11548d002fe1f9b5650cc, 9a738cf170a4a2332ea3a15e23ec65b5757fe4a1, 5d291ef0585ed880ed4dd71ea1a5965e0a65fb53 |
Published upstream
May 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 15, 2026
In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Triple fault if restore host CR3 fails on nested #VMEXIT If loading L1's CR3 fails on a nested #VMEXIT, nested_svm_vmexit() returns an error code that is ignored by most callers, and continues to run L1 with corrupted state. A sane recovery is not possible in this case, and HW behavior is to cause a shutdown. Inject a triple fault instead, and do not return early from nested_svm_vmexit(). Continue cleaning up the vCPU state (e.g. clear pending exceptions), to handle the failure as gracefully as possible. From the APM: Upon #VMEXIT, the processor performs the following actions in order to return to the host execution context: ... if (illegal host state loaded, or exception while loading host state) shutdown else execute first host instruction following the VMRUN Remove the return value of nested_svm_vmexit(), which is mostly unchecked anyway.
Quoted source text, attributed separately from HOL analysis.