CVE-2026-99592: x86/mm: Fix global ASID handed out to two processes
In the Linux kernel, the following vulnerability has been resolved:
x86/mm: Fix global ASID handed out to two processes
On AMD CPUs with INVLPGB, two live processes can get the same MAXASIDAVAILABLE global ASID value. The two then hit each other's TLB entries, so each can read or corrupt the other's memory.
The global ASID space is managed lazily. When a global ASID is freed, its bit is set in the globalasidfreed bitmap. Once the free ASID search reaches the end of the globalasidused bitmap, a global flush is done to really reclaim the lazily freed global ASIDs.
However, the current code can assign the same global ASID to two different processes, if one process is assigned MAXASIDAVAILABLE - 1, another process MAXASIDAVAILABLE, and both stick around (keeping their global ASID numbers in use) until the search wraps around again. At that point a third process could also get assigned MAXASIDAVAILABLE.
the highest ASID stays in use, so it is not handed out again lastglobalasid stays below it, so no reset the clear bits run out findnextzerobit() returns MAXASIDAVAILABLE globalasidavailable > 0, so the failure is not caught MAXASIDAVAILABLE is handed out as an ASID
A search only looks at the bits below MAXASIDAVAILABLE, so it cannot see that this value is in use. The next failed search hands it out again, even if the first process still holds it.
The fix used here is to reset the global ASID space after a failed search, and to search again. If that search fails too, no global ASID is handed out.
The test for !globalasidavailable is removed, because useglobalasid() only calls allocateglobalasid() if globalasidavailable > 0. The remaining test is for a condition that should be impossible.
[ riel: simplify code, massage changelog and comment ]
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 6.12.107-1Fixed in 6.12.117-1Fixed in 7.3.5-1 - Compensating control
Reset the global ASID space after a failed search, then search again.
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
The issue affects Linux kernel systems running on AMD CPUs with INVLPGB. The vulnerable condition involves the kernel's global ASID allocation for live processes.
What is required for exploitation?
The described failure requires global ASID allocation to wrap around while processes holding the highest global ASID values remain live. A third process can then be assigned a global ASID already in use by another live process.
What is the security impact if the ASID collision occurs?
Two processes sharing the same global ASID can use each other's TLB entries. This can allow one process to read or corrupt the other process's memory.
Are affected ASIDs immediately reusable after a process releases them?
No. Global ASIDs are managed lazily: freed ASIDs are recorded in a bitmap and are reclaimed by a global flush when the allocation search reaches the end of the used-ASID bitmap.