CVE-2026-99346
Severity unknownNo known exploitationFix availableKVM: SVM: Trigger new ASID allocation in both VMCBs on pCPU switch
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 10% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Trigger new ASID allocation in both VMCBs on pCPU switch When the pCPU where the VMCB was most recently used is switched, reset the ASID generation in both VMCBs, triggering new ASID allocation for the immediate VMRUN as well as the next VMRUN on the other VMCB. The ASID is shared between vmcb01 and vmcb02, and gets flushed on every nested transition. However, since pCPU tracking is done per VMCB, it is possible for one VMCB to allocate a new ASID when migrated to a new pCPU, and then the other VMCB reuses that ASID on the old pCPU. This can result in the same ASID being used by multiple vCPUs on the old pCPU. Example scenario: - vCPU runs on pCPU A, vmcb01 is active, asid=1. - vCPU migrates to pCPU B, vmcb01 pCPU changes, new asid=2. - Another vCPU runs on pCPU A and allocates asid=2 as well. - vCPU migrates back to pCPU A, and then switches to vmcb02 before it runs again with vmcb01. - No pCPU switch is detected for vmcb02, so VMRUN is done with asid=2. - Two vCPUs end up using asid=2 on the same pCPU. Keep the VMCB dirtying to the active VMCB only. Clean bits are tracked by a pCPU for each VMCB, so do not unnecessarily dirty a VMCB if its pCPU does not change. Additionally, initialize the tracked pCPU for vmcb02 to -1 on nested enablement as hardening, so that a new ASID allocation is always triggered when nested is disabled and re-enabled. No performance regression was noticed when overcommitting L1 vCPUs in L0 (to force rescheduling), pinning L1 L2 vCPUs, and running CPUID in a tight loop bouncing between 2 vCPUs in L2. An alternative (and perhaps more proper) fix would be tracking the ASID per-VMCB instead (e.g. [1]). However, that's a more involved change, and it would result in having different ASIDs for L1 and L2 without actually properly maintaining them. It would probably work because all TLB flushes target the current VMCB, and the other VMCB is always flushed on nested transitions, but the code ends up in an arguably more fragile state. Punt a proper clean fix to an incoming (and overdue) overhaul of SVM's ASID usage [2]. [1] https://lore.kernel.org/lkml/20250205182402.2147495-2-yosry.ahmed@linux.dev [2] https://lore.kernel.org/kvm/20260728003557.1136583-1-yosry@kernel.org
Patching and mitigation
- Patch status
- Fix available (source: CVE record (Linux))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from 193015adf40d0465c240d4e9a7b6e4b84b531f8b before 7d787fb34e825218702496fb0d5892529bea9366 | 7d787fb34e825218702496fb0d5892529bea9366 | CVE Program |
| Linux | Linux | from 193015adf40d0465c240d4e9a7b6e4b84b531f8b before bf260dc9e7b8bfcd06c1a8e739797b1cf0917c72 | bf260dc9e7b8bfcd06c1a8e739797b1cf0917c72 | CVE Program |
| Linux | Linux | from 193015adf40d0465c240d4e9a7b6e4b84b531f8b before 5636d57b61068918085360aaad18ab57872e5800 | 5636d57b61068918085360aaad18ab57872e5800 | CVE Program |
| Linux | Linux | from 193015adf40d0465c240d4e9a7b6e4b84b531f8b before 058173bce103b6ac405b2bbf61e29a7f3767348f | 058173bce103b6ac405b2bbf61e29a7f3767348f | CVE Program |
| Linux | Linux | 5.13 | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.12.117 up to and including 6.12.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.18.61 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.3.2 up to and including 7.3.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.4-rc1 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 5.13 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (Linux)
Vendor guidance and references
- https://git.kernel.org/stable/c/058173bce103b6ac405b2bbf61e29a7f3767348f (opens in a new tab)
- https://git.kernel.org/stable/c/5636d57b61068918085360aaad18ab57872e5800 (opens in a new tab)
- https://git.kernel.org/stable/c/7d787fb34e825218702496fb0d5892529bea9366 (opens in a new tab)
- https://git.kernel.org/stable/c/bf260dc9e7b8bfcd06c1a8e739797b1cf0917c72 (opens in a new tab)