Answer in brief
CVE-2026-46076 records a High severity (CVSS 7.9) vulnerability in KVM: nSVM: Raise #UD if unhandled VMMCALL isn't intercepted by L1. 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.
CVSS is 7.9. 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 | >=3f4a812edf5cb0a50e65fbdfafdb3e688da18f16 <924d721fae95687acedbaf624a094ed0e8b67104 || >=3f4a812edf5cb0a50e65fbdfafdb3e688da18f16 <009c0f726abeaa67aad1d96b883bdce01d405ce2 || >=3f4a812edf5cb0a50e65fbdfafdb3e688da18f16 <5fb4a5f361565f5b629d8a8fe5288ce8463c5727 || >=3f4a812edf5cb0a50e65fbdfafdb3e688da18f16 <c36991c6f8d2ab56ee67aff04e3c357f45cfc76c | 924d721fae95687acedbaf624a094ed0e8b67104, 009c0f726abeaa67aad1d96b883bdce01d405ce2, 5fb4a5f361565f5b629d8a8fe5288ce8463c5727, c36991c6f8d2ab56ee67aff04e3c357f45cfc76c |
| Linux/Linuxgeneric | 6.2 | Not reported |
Published upstream
May 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Raise #UD if unhandled VMMCALL isn't intercepted by L1 Explicitly synthesize a #UD for VMMCALL if L2 is active, L1 does NOT want to intercept VMMCALL, nested_svm_l2_tlb_flush_enabled() is true, and the hypercall is something other than one of the supported Hyper-V hypercalls. When all of the above conditions are met, KVM will intercept VMMCALL but never forward it to L1, i.e. will let L2 make hypercalls as if it were L1. The TLFS says a whole lot of nothing about this scenario, so go with the architectural behavior, which says that VMMCALL #UDs if it's not intercepted. Opportunistically do a 2-for-1 stub trade by stub-ifying the new API instead of the helpers it uses. The last remaining "single" stub will soon be dropped as well. [sean: rewrite changelog and comment, tag for stable, remove defunct stubs]
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-46076 records a High severity (CVSS 7.9) vulnerability in KVM: nSVM: Raise #UD if unhandled VMMCALL isn't intercepted by L1. 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.
CVSS is 7.9. 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 | >=3f4a812edf5cb0a50e65fbdfafdb3e688da18f16 <924d721fae95687acedbaf624a094ed0e8b67104 || >=3f4a812edf5cb0a50e65fbdfafdb3e688da18f16 <009c0f726abeaa67aad1d96b883bdce01d405ce2 || >=3f4a812edf5cb0a50e65fbdfafdb3e688da18f16 <5fb4a5f361565f5b629d8a8fe5288ce8463c5727 || >=3f4a812edf5cb0a50e65fbdfafdb3e688da18f16 <c36991c6f8d2ab56ee67aff04e3c357f45cfc76c | 924d721fae95687acedbaf624a094ed0e8b67104, 009c0f726abeaa67aad1d96b883bdce01d405ce2, 5fb4a5f361565f5b629d8a8fe5288ce8463c5727, c36991c6f8d2ab56ee67aff04e3c357f45cfc76c |
| Linux/Linuxgeneric | 6.2 | Not reported |
Published upstream
May 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Raise #UD if unhandled VMMCALL isn't intercepted by L1 Explicitly synthesize a #UD for VMMCALL if L2 is active, L1 does NOT want to intercept VMMCALL, nested_svm_l2_tlb_flush_enabled() is true, and the hypercall is something other than one of the supported Hyper-V hypercalls. When all of the above conditions are met, KVM will intercept VMMCALL but never forward it to L1, i.e. will let L2 make hypercalls as if it were L1. The TLFS says a whole lot of nothing about this scenario, so go with the architectural behavior, which says that VMMCALL #UDs if it's not intercepted. Opportunistically do a 2-for-1 stub trade by stub-ifying the new API instead of the helpers it uses. The last remaining "single" stub will soon be dropped as well. [sean: rewrite changelog and comment, tag for stable, remove defunct stubs]
Quoted source text, attributed separately from HOL analysis.