KVM: SVM: Trigger new ASID allocation in both VMCBs on pCPU switch
Severity and exploitation
KEV coverage does not rule out exploitation.
Assessment vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HSeverity
high8.8CVSS measures technical severity, not the likelihood of an attack.
Known exploitation
Not listed in the checked CISA KEV catalog
Absence from CISA KEV does not rule out attacks.
Public exploit
Not established by this record
Missing evidence does not mean no public exploit exists.
Remediation
Fix status not established
No structured fix or guidance is available here. Check the latest publisher advisory.
What this means
In the Linux kernel, the following vulnerability has been resolved:
Source excerpt · LinuxAttack conditions
No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.
Review supporting sources →Affected versions
Check the exact model, release, and any platform requirements against your installation.
Linux · Linux
Linux
4 ranges
Linux · Linux
Linux
Compare with this publisher’s ranges. This does not inspect your installation.
affected
193015adf40d0465c240d4e9a7b6e4b84b531f8b → before 5636d57b61068918085360aaad18ab57872e5800
git versions
193015adf40d0465c240d4e9a7b6e4b84b531f8b → before 058173bce103b6ac405b2bbf61e29a7f3767348f
git versions
193015adf40d0465c240d4e9a7b6e4b84b531f8b → before 7d787fb34e825218702496fb0d5892529bea9366
git versions
193015adf40d0465c240d4e9a7b6e4b84b531f8b → before bf260dc9e7b8bfcd06c1a8e739797b1cf0917c72
git versions
Other versions: unaffected
Linux · Linux
Linux
6 ranges
Linux · Linux
Linux
Compare with this publisher’s ranges. This does not inspect your installation.
affected
5.13
unaffected
0 → before 5.13
semver versions
6.12.117 → through 6.12.*
semver versions
6.18.61 → through 6.18.*
semver versions
7.3.2 → through 7.3.*
semver versions
7.4-rc1 → through *
original_commit_for_fix versions
Other versions: affected
What to do
Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.
No structured fix or remediation guidance is available here. Check the full source description and vendor’s latest advisory for a patch or workaround; do not assume another version is safe.
cve.new guidance unless attributed to a publisher. This page does not inspect your installation.
Public exploit evidence
No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.
Original source description
Read the full publisher 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
References
4 sourcesInside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-99346View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Environment requirements
These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.
Linux · platform conditions
Any condition may hold
Vulnerable product
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*From (inclusive): 5.13
Before: 6.12.117
Vulnerable product
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*From (inclusive): 5.13
Before: 6.18.61
Vulnerable product
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*From (inclusive): 5.13
Before: 7.3.2
Vulnerable product
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*From (inclusive): 5.13
Before: 7.4-rc1
Applicability preview
[
{
"nodes": [
{
"operator": "OR",
"negate": false,
"cpeMatch": [
{
"vulnerable": true,
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "5.13",
"versionEndExcluding": "6.12.117"
},
{
"vulnerable": true,
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "5.13",
"versionEndExcluding": "6.18.61"
},
{
"vulnerable": true,
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "5.13",
"versionEndExcluding": "7.3.2"
},
{
"vulnerable": true,
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "5.13",
"versionEndExcluding": "7.4-rc1"
}
]
}
]
}
]Contributing organizations · 1
Assigning organization
Timeline
All times UTCAdvisory published
Publication date supplied by the source.
Source updated
Latest modification date supplied by the source.
Last imported by cve.new
Latest catalog import, not the date we first saw this advisory.
What changed
Follow changes- CVE · CVE-2026-99346
Observed 2026-11-22T11:20:47.024Z · upstream updated 2026-11-22T11:07:48.175Z
Severity assessment changed
before
[]
after
[ { "source": "Linux", "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H", "score": 8.8 } ] - CVE · CVE-2026-99346
Observed 2026-11-20T05:58:44.204Z · upstream updated 2026-11-20T05:11:38.533Z
Product or version evidence changed
before
[ { "vendor": "Linux", "name": "Linux", "platforms": [], "versions": [ { "version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2", "status": "affected", "lessThan": "5636d57b61068918085360aaad18ab57872e5800", "versionType": "git" }, { "version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2", "status": "affected", "lessThan": "058173bce103b6ac405b2bbf61e29a7f3767348f", "versionType": "git" }, { "version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2", "status": "affected", "lessThan": "7d787fb34e825218702496fb0d5892529bea9366", "versionType": "git" }, { "version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2", "status": "affected", "lessThan": "bf260dc9e7b8bfcd06c1a8e739797b1cf0917c72", "versionType": "git" }, { "version": "0", "status": "affected", "lessThan": "6.12.117", "versionType": "semver" }, { "version": "0", "status": "affected", "lessThan": "6.18.61", "versionType": "semver" }, { "version": "0", "status": "affected", "lessThan": "7.3.2", "versionType": "semver" } ], "defaultStatus": "unaffected", "cpes": [], "source": "Linux", "url": "https://www.cve.org/CVERecord?id=CVE-2026-99346" }, { "vendor": "Linux", "name": "Linux", "platforms": [], "versions": [ { "version": "6.12.117", "status": "unaffected", "lessThanOrEqual": "6.12.*", "versionType": "semver" }, { "version": "6.18.61", "status": "unaffected", "lessThanOrEqual": "6.18.*", "versionType": "semver" }, { "version": "7.3.2", "status": "unaffected", "lessThanOrEqual": "7.3.*", "versionType": "semver" }, { "version": "7.4-rc1", "status": "unaffected", "lessThanOrEqual": "*", "versionType": "original_commit_for_fix" } ], "defaultStatus": "affected", "cpes": [], "source": "Linux", "url": "https://www.cve.org/CVERecord?id=CVE-2026-99346" } ]after
[ { "vendor": "Linux", "name": "Linux", "platforms": [], "versions": [ { "version": "193015adf40d0465c240d4e9a7b6e4b84b531f8b", "status": "affected", "lessThan": "5636d57b61068918085360aaad18ab57872e5800", "versionType": "git" }, { "version": "193015adf40d0465c240d4e9a7b6e4b84b531f8b", "status": "affected", "lessThan": "058173bce103b6ac405b2bbf61e29a7f3767348f", "versionType": "git" }, { "version": "193015adf40d0465c240d4e9a7b6e4b84b531f8b", "status": "affected", "lessThan": "7d787fb34e825218702496fb0d5892529bea9366", "versionType": "git" }, { "version": "193015adf40d0465c240d4e9a7b6e4b84b531f8b", "status": "affected", "lessThan": "bf260dc9e7b8bfcd06c1a8e739797b1cf0917c72", "versionType": "git" } ], "defaultStatus": "unaffected", "cpes": [], "source": "Linux", "url": "https://www.cve.org/CVERecord?id=CVE-2026-99346" }, { "vendor": "Linux", "name": "Linux", "platforms": [], "versions": [ { "version": "5.13", "status": "affected" }, { "version": "0", "status": "unaffected", "lessThan": "5.13", "versionType": "semver" }, { "version": "6.12.117", "status": "unaffected", "lessThanOrEqual": "6.12.*", "versionType": "semver" }, { "version": "6.18.61", "status": "unaffected", "lessThanOrEqual": "6.18.*", "versionType": "semver" }, { "version": "7.3.2", "status": "unaffected", "lessThanOrEqual": "7.3.*", "versionType": "semver" }, { "version": "7.4-rc1", "status": "unaffected", "lessThanOrEqual": "*", "versionType": "original_commit_for_fix" } ], "defaultStatus": "affected", "cpes": [], "source": "Linux", "url": "https://www.cve.org/CVERecord?id=CVE-2026-99346" } ]Environment requirements changed
before
[ { "source": "Linux", "statements": [ { "nodes": [ { "operator": "OR", "negate": false, "cpeMatch": [ { "vulnerable": true, "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" } ] } ] } ] } ]after
[ { "source": "Linux", "statements": [ { "nodes": [ { "operator": "OR", "negate": false, "cpeMatch": [ { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "5.13", "versionEndExcluding": "6.12.117" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "5.13", "versionEndExcluding": "6.18.61" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "5.13", "versionEndExcluding": "7.3.2" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "5.13", "versionEndExcluding": "7.4-rc1" } ] } ] } ] } ]
Large field values are marked as truncated previews. Original source snapshots remain retained.
Showing up to 50 most recent observed changes.