CVE-2026-99346 (GCVE-0-2026-99346)
Vulnerability from cvelistv5 – Published: 2026-11-19 14:22 – Updated: 2026-11-19 14:36| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 , < 5636d57b61068918085360aaad18ab57872e5800
(git)
Affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 , < 058173bce103b6ac405b2bbf61e29a7f3767348f (git) Affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 , < 7d787fb34e825218702496fb0d5892529bea9366 (git) Affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 , < bf260dc9e7b8bfcd06c1a8e739797b1cf0917c72 (git) Affected: 0 , < 6.12.117 (semver) Affected: 0 , < 6.18.61 (semver) Affected: 0 , < 7.3.2 (semver) |
guessed | |
| Linux | Linux |
Unaffected:
6.12.117 , ≤ 6.12.*
(semver)
Unaffected: 6.18.61 , ≤ 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",
"arch/x86/kvm/svm/svm.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "5636d57b61068918085360aaad18ab57872e5800",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "058173bce103b6ac405b2bbf61e29a7f3767348f",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "7d787fb34e825218702496fb0d5892529bea9366",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "bf260dc9e7b8bfcd06c1a8e739797b1cf0917c72",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "6.12.117",
"status": "affected",
"version": "0",
"versionType": "semver"
},
{
"lessThan": "6.18.61",
"status": "affected",
"version": "0",
"versionType": "semver"
},
{
"lessThan": "7.3.2",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"arch/x86/kvm/svm/nested.c",
"arch/x86/kvm/svm/svm.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.117",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.61",
"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.117",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.61",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3.2",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.4-rc1",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Trigger new ASID allocation in both VMCBs on pCPU switch\n\nWhen the pCPU where the VMCB was most recently used is switched, reset\nthe ASID generation in both VMCBs, triggering new ASID allocation for\nthe immediate VMRUN as well as the next VMRUN on the other VMCB.\n\nThe ASID is shared between vmcb01 and vmcb02, and gets flushed on every\nnested transition. However, since pCPU tracking is done per VMCB, it is\npossible for one VMCB to allocate a new ASID when migrated to a new\npCPU, and then the other VMCB reuses that ASID on the old pCPU. This can\nresult in the same ASID being used by multiple vCPUs on the old pCPU.\n\nExample scenario:\n- vCPU runs on pCPU A, vmcb01 is active, asid=1.\n- vCPU migrates to pCPU B, vmcb01 pCPU changes, new asid=2.\n- Another vCPU runs on pCPU A and allocates asid=2 as well.\n- vCPU migrates back to pCPU A, and then switches to vmcb02 before it\n runs again with vmcb01.\n- No pCPU switch is detected for vmcb02, so VMRUN is done with asid=2.\n- Two vCPUs end up using asid=2 on the same pCPU.\n\nKeep the VMCB dirtying to the active VMCB only. Clean bits are tracked\nby a pCPU for each VMCB, so do not unnecessarily dirty a VMCB if its\npCPU does not change.\n\nAdditionally, initialize the tracked pCPU for vmcb02 to -1 on nested\nenablement as hardening, so that a new ASID allocation is always\ntriggered when nested is disabled and re-enabled.\n\nNo performance regression was noticed when overcommitting L1 vCPUs in L0\n(to force rescheduling), pinning L1 \u003c-\u003e L2 vCPUs, and running CPUID in a\ntight loop bouncing between 2 vCPUs in L2.\n\nAn alternative (and perhaps more proper) fix would be tracking the ASID\nper-VMCB instead (e.g. [1]). However, that\u0027s a more involved change, and\nit would result in having different ASIDs for L1 and L2 without actually\nproperly maintaining them. It would probably work because all TLB\nflushes target the current VMCB, and the other VMCB is always flushed on\nnested transitions, but the code ends up in an arguably more fragile\nstate. Punt a proper clean fix to an incoming (and overdue) overhaul of\nSVM\u0027s ASID usage [2].\n\n[1] https://lore.kernel.org/lkml/20250205182402.2147495-2-yosry.ahmed@linux.dev\n[2] https://lore.kernel.org/kvm/20260728003557.1136583-1-yosry@kernel.org"
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:36:24.887Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/5636d57b61068918085360aaad18ab57872e5800"
},
{
"url": "https://git.kernel.org/stable/c/058173bce103b6ac405b2bbf61e29a7f3767348f"
},
{
"url": "https://git.kernel.org/stable/c/7d787fb34e825218702496fb0d5892529bea9366"
},
{
"url": "https://git.kernel.org/stable/c/bf260dc9e7b8bfcd06c1a8e739797b1cf0917c72"
}
],
"title": "KVM: SVM: Trigger new ASID allocation in both VMCBs on pCPU switch",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99346",
"datePublished": "2026-11-19T14:22:01.304Z",
"dateReserved": "2026-09-25T10:25:14.409Z",
"dateUpdated": "2026-11-19T14:36:24.887Z",
"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",
"arch/x86/kvm/svm/svm.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "5636d57b61068918085360aaad18ab57872e5800",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "058173bce103b6ac405b2bbf61e29a7f3767348f",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "7d787fb34e825218702496fb0d5892529bea9366",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "bf260dc9e7b8bfcd06c1a8e739797b1cf0917c72",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "6.12.117",
"status": "affected",
"version": "0",
"versionType": "semver"
},
{
"lessThan": "6.18.61",
"status": "affected",
"version": "0",
"versionType": "semver"
},
{
"lessThan": "7.3.2",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"arch/x86/kvm/svm/nested.c",
"arch/x86/kvm/svm/svm.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.117",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.61",
"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: SVM: Trigger new ASID allocation in both VMCBs on pCPU switch\n\nWhen the pCPU where the VMCB was most recently used is switched, reset\nthe ASID generation in both VMCBs, triggering new ASID allocation for\nthe immediate VMRUN as well as the next VMRUN on the other VMCB.\n\nThe ASID is shared between vmcb01 and vmcb02, and gets flushed on every\nnested transition. However, since pCPU tracking is done per VMCB, it is\npossible for one VMCB to allocate a new ASID when migrated to a new\npCPU, and then the other VMCB reuses that ASID on the old pCPU. This can\nresult in the same ASID being used by multiple vCPUs on the old pCPU.\n\nExample scenario:\n- vCPU runs on pCPU A, vmcb01 is active, asid=1.\n- vCPU migrates to pCPU B, vmcb01 pCPU changes, new asid=2.\n- Another vCPU runs on pCPU A and allocates asid=2 as well.\n- vCPU migrates back to pCPU A, and then switches to vmcb02 before it\n runs again with vmcb01.\n- No pCPU switch is detected for vmcb02, so VMRUN is done with asid=2.\n- Two vCPUs end up using asid=2 on the same pCPU.\n\nKeep the VMCB dirtying to the active VMCB only. Clean bits are tracked\nby a pCPU for each VMCB, so do not unnecessarily dirty a VMCB if its\npCPU does not change.\n\nAdditionally, initialize the tracked pCPU for vmcb02 to -1 on nested\nenablement as hardening, so that a new ASID allocation is always\ntriggered when nested is disabled and re-enabled.\n\nNo performance regression was noticed when overcommitting L1 vCPUs in L0\n(to force rescheduling), pinning L1 \u003c-\u003e L2 vCPUs, and running CPUID in a\ntight loop bouncing between 2 vCPUs in L2.\n\nAn alternative (and perhaps more proper) fix would be tracking the ASID\nper-VMCB instead (e.g. [1]). However, that\u0027s a more involved change, and\nit would result in having different ASIDs for L1 and L2 without actually\nproperly maintaining them. It would probably work because all TLB\nflushes target the current VMCB, and the other VMCB is always flushed on\nnested transitions, but the code ends up in an arguably more fragile\nstate. Punt a proper clean fix to an incoming (and overdue) overhaul of\nSVM\u0027s ASID usage [2].\n\n[1] https://lore.kernel.org/lkml/20250205182402.2147495-2-yosry.ahmed@linux.dev\n[2] https://lore.kernel.org/kvm/20260728003557.1136583-1-yosry@kernel.org"
}
],
"id": "CVE-2026-99346",
"lastModified": "2026-11-19T15:17:45.830",
"metrics": {},
"published": "2026-11-19T15:17:45.830",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/058173bce103b6ac405b2bbf61e29a7f3767348f"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/5636d57b61068918085360aaad18ab57872e5800"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/7d787fb34e825218702496fb0d5892529bea9366"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/bf260dc9e7b8bfcd06c1a8e739797b1cf0917c72"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Important",
"current_release_date": "2026-11-19T16:40:27+00:00",
"cve": "CVE-2026-99346",
"id": "CVE-2026-99346",
"initial_release_date": "2026-11-19T14:22:01.304000+00:00",
"product_status:known_affected": "162",
"product_status:known_not_affected": "42",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: kernel: Information disclosure via improper ASID allocation in KVM SVM",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99346.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.