CVE-2026-99345 (GCVE-0-2026-99345)
Vulnerability from cvelistv5 – Published: 2026-11-19 14:21 – Updated: 2026-11-19 14:36| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
cc440cdad5b7a4c1de12dace725209eb3e0cf663 , < c0b29d523ef363d1d7ccfb3199f0126b22a61f66
(git)
Affected: cc440cdad5b7a4c1de12dace725209eb3e0cf663 , < 98362865bb626bb5e76cede98555d7cd4fefc016 (git) Affected: cc440cdad5b7a4c1de12dace725209eb3e0cf663 , < 81c460713ca62fa33ee1241fda1ddaf099facb32 (git) Affected: cc440cdad5b7a4c1de12dace725209eb3e0cf663 , < 5dc500a354cc8e109df678076ae3488094649468 (git) |
guessed | |
| Linux | Linux |
Affected:
5.8
Unaffected: 0 , < 5.8 (semver) Unaffected: 6.12.118 , ≤ 6.12.* (semver) Unaffected: 6.18.64 , ≤ 6.18.* (semver) Unaffected: 7.3.2 , ≤ 7.3.* (semver) Unaffected: 7.4-rc1 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"arch/x86/kvm/svm/nested.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "c0b29d523ef363d1d7ccfb3199f0126b22a61f66",
"status": "affected",
"version": "cc440cdad5b7a4c1de12dace725209eb3e0cf663",
"versionType": "git"
},
{
"lessThan": "98362865bb626bb5e76cede98555d7cd4fefc016",
"status": "affected",
"version": "cc440cdad5b7a4c1de12dace725209eb3e0cf663",
"versionType": "git"
},
{
"lessThan": "81c460713ca62fa33ee1241fda1ddaf099facb32",
"status": "affected",
"version": "cc440cdad5b7a4c1de12dace725209eb3e0cf663",
"versionType": "git"
},
{
"lessThan": "5dc500a354cc8e109df678076ae3488094649468",
"status": "affected",
"version": "cc440cdad5b7a4c1de12dace725209eb3e0cf663",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"arch/x86/kvm/svm/nested.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.8"
},
{
"lessThan": "5.8",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.118",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.64",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.2",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.118",
"versionStartIncluding": "5.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.64",
"versionStartIncluding": "5.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3.2",
"versionStartIncluding": "5.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.4-rc1",
"versionStartIncluding": "5.8",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: nSVM: Reject KVM_SET_NESTED_STATE if L1 has EFER.LMA=1 \u0026\u0026 EFER.LME=0\n\nReject KVM_SET_NESTED_STATE if the incoming L1 host state has what is\neffectively an impossible EFER combination of LMA=1 but LME=0, i.e. if the\nstate says long mode is active but not enabled. Unlike VMX, SVM doesn\u0027t\nhave an explicit consistent check for the illegal combination; presumably\nhardware simply ignores EFER.LMA if EFER.LME=0.\n\nUnfortunately, KVM doesn\u0027t ignore EFER.LMA in this case and consumes the\nillegal state when constructing the shadow MMU for L2. E.g. if userspace\nalso clears CR4.PAE, then kvm_calc_cpu_role() will compute a role with 4 or\n5 levels of paging, but shadow_mmu_init_context() will wire up the MMU to\nuse the paging32 template, which maxes out its levels at 2.\n\nNote, the \"real badness\" is effectively the same as what happened with the\nnVMX bug fixed by commit 112e66017bff (\"KVM: nVMX: add missing consistency\nchecks for CR0 and CR4\"). Unfortunately, the sanity check added by commit\n72e2fb24a0b0 (\"KVM: x86/mmu: Bug the VM if a vCPU ends up in long mode\nwithout PAE enabled\") doesn\u0027t work for this case, since L2 state is active\nat the time of the page fault, but it\u0027s L1 that has the bad state."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:36:13.477Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/c0b29d523ef363d1d7ccfb3199f0126b22a61f66"
},
{
"url": "https://git.kernel.org/stable/c/98362865bb626bb5e76cede98555d7cd4fefc016"
},
{
"url": "https://git.kernel.org/stable/c/81c460713ca62fa33ee1241fda1ddaf099facb32"
},
{
"url": "https://git.kernel.org/stable/c/5dc500a354cc8e109df678076ae3488094649468"
}
],
"title": "KVM: nSVM: Reject KVM_SET_NESTED_STATE if L1 has EFER.LMA=1 \u0026\u0026 EFER.LME=0",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99345",
"datePublished": "2026-11-19T14:21:53.509Z",
"dateReserved": "2026-09-25T10:25:14.409Z",
"dateUpdated": "2026-11-19T14:36:13.477Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"arch/x86/kvm/svm/nested.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "c0b29d523ef363d1d7ccfb3199f0126b22a61f66",
"status": "affected",
"version": "cc440cdad5b7a4c1de12dace725209eb3e0cf663",
"versionType": "git"
},
{
"lessThan": "98362865bb626bb5e76cede98555d7cd4fefc016",
"status": "affected",
"version": "cc440cdad5b7a4c1de12dace725209eb3e0cf663",
"versionType": "git"
},
{
"lessThan": "81c460713ca62fa33ee1241fda1ddaf099facb32",
"status": "affected",
"version": "cc440cdad5b7a4c1de12dace725209eb3e0cf663",
"versionType": "git"
},
{
"lessThan": "5dc500a354cc8e109df678076ae3488094649468",
"status": "affected",
"version": "cc440cdad5b7a4c1de12dace725209eb3e0cf663",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"arch/x86/kvm/svm/nested.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.8"
},
{
"lessThan": "5.8",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.118",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.64",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.2",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: nSVM: Reject KVM_SET_NESTED_STATE if L1 has EFER.LMA=1 \u0026\u0026 EFER.LME=0\n\nReject KVM_SET_NESTED_STATE if the incoming L1 host state has what is\neffectively an impossible EFER combination of LMA=1 but LME=0, i.e. if the\nstate says long mode is active but not enabled. Unlike VMX, SVM doesn\u0027t\nhave an explicit consistent check for the illegal combination; presumably\nhardware simply ignores EFER.LMA if EFER.LME=0.\n\nUnfortunately, KVM doesn\u0027t ignore EFER.LMA in this case and consumes the\nillegal state when constructing the shadow MMU for L2. E.g. if userspace\nalso clears CR4.PAE, then kvm_calc_cpu_role() will compute a role with 4 or\n5 levels of paging, but shadow_mmu_init_context() will wire up the MMU to\nuse the paging32 template, which maxes out its levels at 2.\n\nNote, the \"real badness\" is effectively the same as what happened with the\nnVMX bug fixed by commit 112e66017bff (\"KVM: nVMX: add missing consistency\nchecks for CR0 and CR4\"). Unfortunately, the sanity check added by commit\n72e2fb24a0b0 (\"KVM: x86/mmu: Bug the VM if a vCPU ends up in long mode\nwithout PAE enabled\") doesn\u0027t work for this case, since L2 state is active\nat the time of the page fault, but it\u0027s L1 that has the bad state."
}
],
"id": "CVE-2026-99345",
"lastModified": "2026-11-19T15:17:45.720",
"metrics": {},
"published": "2026-11-19T15:17:45.720",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/5dc500a354cc8e109df678076ae3488094649468"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/81c460713ca62fa33ee1241fda1ddaf099facb32"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/98362865bb626bb5e76cede98555d7cd4fefc016"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/c0b29d523ef363d1d7ccfb3199f0126b22a61f66"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-19T21:50:28+00:00",
"cve": "CVE-2026-99345",
"id": "CVE-2026-99345",
"initial_release_date": "2026-11-19T14:21:53.509000+00:00",
"product_status:known_affected": "162",
"product_status:known_not_affected": "42",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: kernel: Denial of Service via invalid nested processor state in KVM nSVM",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99345.json",
"version": "3"
}
}
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.