Skip to main content
VulnerabilityPublished

CVE-2026-99592: Linux kernel · x86/mm: Fix global ASID handed out to two processes

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in 02938c10d9e5c7631c8dbd6c48517805c1edf0a6 : update Linux kernel when convenient.

Data as of 20 Nov 2026, 06:19 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 02938c10d9e5c7631c8dbd6c48517805c1edf0a6, 25bf240e1c755aaef670680a6de03f9f561c86f5, 5cdc3746fa163fb4e8d05fa3cabf46bc6aa7df75

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Linux kernel to 02938c10d9e5c7631c8dbd6c48517805c1edf0a6, 25bf240e1c755aaef670680a6de03f9f561c86f5 or 5cdc3746fa163fb4e8d05fa3cabf46bc6aa7df75.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ d504d1247e369e82c30588b296cc45a85a1ecc12, < 02938c10d9e5c7631c8dbd6c48517805c1edf0a6
Fixed in
  • 02938c10d9e5c7631c8dbd6c48517805c1edf0a6
LinuxLinuxAffected
  • ≥ d504d1247e369e82c30588b296cc45a85a1ecc12, < 25bf240e1c755aaef670680a6de03f9f561c86f5
Fixed in
  • 25bf240e1c755aaef670680a6de03f9f561c86f5
LinuxLinuxAffected
  • ≥ d504d1247e369e82c30588b296cc45a85a1ecc12, < 5cdc3746fa163fb4e8d05fa3cabf46bc6aa7df75
Fixed in
  • 5cdc3746fa163fb4e8d05fa3cabf46bc6aa7df75
LinuxLinuxAffected
  • =6.15
Fixed in–

Description

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 ]

References

Community reviews

Loading reviews…