Answer in brief
CVE-2022-2196 records a Unknown severity vulnerability in Speculative execution attacks in KVM VMX. The current sources do not mark it as known exploited. The current feed maps Linux/Linux Kernel (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-2022-2196 records a Unknown severity vulnerability in Speculative execution attacks in KVM VMX. The current sources do not mark it as known exploited. The current feed maps Linux/Linux Kernel (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 Kernel (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linux Kernelgeneric | >=64b8f33b2e1e687d465b5cb382e7bec495f1e026 <f93a1a5bdcdd122aae0a3eab7a52c15b71fb725b || >=e089a83fbc55b8057f332c00f125acaa02b08ef7 <2e7eab81425ad6c875f2ed47c0ce01e78afc38a5 || >=02a3868d18fe639363f1cea6e6d7914513198e43 <2e7eab81425ad6c875f2ed47c0ce01e78afc38a5 || >=5c911beff20aa8639e7a1f28988736c13e03ed54 <1b0cafaae8884726c597caded50af185ffc13349 || >=5c911beff20aa8639e7a1f28988736c13e03ed54 <6b539a7dbb49250f92515c2ba60aea239efc9e35 || >=5c911beff20aa8639e7a1f28988736c13e03ed54 <63fada296062e91ad9f871970d4e7f19e21a6a15 || >=5c911beff20aa8639e7a1f28988736c13e03ed54 <2e7eab81425ad6c875f2ed47c0ce01e78afc38a5 || >=5.4.47 <5.4.233 || >=5.6.19 <5.7.0 || >=5.7.3 <5.8.0 || >=5.8.0 <5.10.170 || >=5.11.0 <5.15.96 || >=5.16.0 <6.1.14 | f93a1a5bdcdd122aae0a3eab7a52c15b71fb725b, 2e7eab81425ad6c875f2ed47c0ce01e78afc38a5, 1b0cafaae8884726c597caded50af185ffc13349, 6b539a7dbb49250f92515c2ba60aea239efc9e35, 63fada296062e91ad9f871970d4e7f19e21a6a15, 5.4.233, 5.7.0, 5.8.0, 5.10.170, 5.15.96, 6.1.14 |
Published upstream
Jan 9, 2023
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 7, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 7, 2026
A regression exists in the Linux Kernel within KVM: nVMX that allowed for speculative execution attacks. L2 can carry out Spectre v2 attacks on L1 due to L1 thinking it doesn't need retpolines or IBPB after running L2 due to KVM (L0) advertising eIBRS support to L1. An attacker at L2 with code execution can execute code on an indirect branch on the host machine. We recommend upgrading to Kernel 6.2 or applying the relevant stable backports (v5.4.233, v5.10.170, v5.15.96, v6.1.14).
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 Kernel (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linux Kernelgeneric | >=64b8f33b2e1e687d465b5cb382e7bec495f1e026 <f93a1a5bdcdd122aae0a3eab7a52c15b71fb725b || >=e089a83fbc55b8057f332c00f125acaa02b08ef7 <2e7eab81425ad6c875f2ed47c0ce01e78afc38a5 || >=02a3868d18fe639363f1cea6e6d7914513198e43 <2e7eab81425ad6c875f2ed47c0ce01e78afc38a5 || >=5c911beff20aa8639e7a1f28988736c13e03ed54 <1b0cafaae8884726c597caded50af185ffc13349 || >=5c911beff20aa8639e7a1f28988736c13e03ed54 <6b539a7dbb49250f92515c2ba60aea239efc9e35 || >=5c911beff20aa8639e7a1f28988736c13e03ed54 <63fada296062e91ad9f871970d4e7f19e21a6a15 || >=5c911beff20aa8639e7a1f28988736c13e03ed54 <2e7eab81425ad6c875f2ed47c0ce01e78afc38a5 || >=5.4.47 <5.4.233 || >=5.6.19 <5.7.0 || >=5.7.3 <5.8.0 || >=5.8.0 <5.10.170 || >=5.11.0 <5.15.96 || >=5.16.0 <6.1.14 | f93a1a5bdcdd122aae0a3eab7a52c15b71fb725b, 2e7eab81425ad6c875f2ed47c0ce01e78afc38a5, 1b0cafaae8884726c597caded50af185ffc13349, 6b539a7dbb49250f92515c2ba60aea239efc9e35, 63fada296062e91ad9f871970d4e7f19e21a6a15, 5.4.233, 5.7.0, 5.8.0, 5.10.170, 5.15.96, 6.1.14 |
Published upstream
Jan 9, 2023
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 7, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 7, 2026
A regression exists in the Linux Kernel within KVM: nVMX that allowed for speculative execution attacks. L2 can carry out Spectre v2 attacks on L1 due to L1 thinking it doesn't need retpolines or IBPB after running L2 due to KVM (L0) advertising eIBRS support to L1. An attacker at L2 with code execution can execute code on an indirect branch on the host machine. We recommend upgrading to Kernel 6.2 or applying the relevant stable backports (v5.4.233, v5.10.170, v5.15.96, v6.1.14).
Quoted source text, attributed separately from HOL analysis.