CVE-2026-99592

Source
https://cve.org/CVERecord?id=CVE-2026-99592
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99592.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-99592
Published
2026-11-20T05:49:20Z
Modified
2026-11-20T07:00:44Z
Summary
x86/mm: Fix global ASID handed out to two processes
Details

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 MAX_ASID_AVAILABLE 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 global_asid_freed bitmap. Once the free ASID search reaches the end of the global_asid_used 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 MAX_ASID_AVAILABLE - 1, another process MAX_ASID_AVAILABLE, 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 MAX_ASID_AVAILABLE.

the highest ASID stays in use, so it is not handed out again
  last_global_asid stays below it, so no reset
    the clear bits run out
      find_next_zero_bit() returns MAX_ASID_AVAILABLE
        global_asid_available > 0, so the failure is not caught
          MAX_ASID_AVAILABLE is handed out as an ASID

A search only looks at the bits below MAX_ASID_AVAILABLE, 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 !global_asid_available is removed, because use_global_asid() only calls allocate_global_asid() if global_asid_available > 0. The remaining test is for a condition that should be impossible.

[ riel: simplify code, massage changelog and comment ]

Database specific
{
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99592.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
d504d1247e369e82c30588b296cc45a85a1ecc12
Fixed
25bf240e1c755aaef670680a6de03f9f561c86f5
Fixed
02938c10d9e5c7631c8dbd6c48517805c1edf0a6
Fixed
5cdc3746fa163fb4e8d05fa3cabf46bc6aa7df75

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99592.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
6.15.0
Fixed
6.18.64
Type
ECOSYSTEM
Events
Introduced
6.19.0
Fixed
7.3.5

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99592.json"