CVE-2026-89917
Severity unknownNo known exploitationFix availableKVM: arm64: Handle VNCR TLB invalidation race with vcpu_put() VNCR unmapping
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 11% 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: arm64: Handle VNCR TLB invalidation race with vcpu_put() VNCR unmapping While VNCR TLB invalidation always occurs under the MMU lock, vcpu_put() doesn't, while it unmaps the VNCR page. The problem is that the invalidation evaluates vncr_tlb::cpu to decide whether an unmapping needs to take place (cpu != -1) before performing it. On the other hand, this_cpu_reset_vncr_fixmap() unconditionally unmaps if L1_VNCR_MAPPED is set. These two obviously can race, with a TOCTOU pattern on the TLBI path, and a BUG_ON() on the vcpu_put() path. And the two can end-up calling vncr_fixmap(-1), with extra lethal effects. Move the reset of vncr_tlb::cpu to -1 to a common function, and make this update atomic so that only a single thread can reset the field and perform the corresponding unmap. The vcpu_put() still need to unconditionally unmap the current VNCR to close another ugly race. Finally, the assignment of vncr_tlb::cpu is moved to be kept in sync with the actual mapping, similar to L1_VNCR_MAPPED being set.
Patching and mitigation
- Patch status
- Fix available (source: Microsoft MSRC)
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- msrc.microsoft.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from 7270cc9157f474dfc46750a34c9d7defc686b2eb before 5cbd8761d001c11ada73b1753d772c4745a70e72 | 5cbd8761d001c11ada73b1753d772c4745a70e72 | CVE Program |
| Linux | Linux | from 7270cc9157f474dfc46750a34c9d7defc686b2eb before 9065c1261f8a05c6a7a2d90048c7c0665ab2896d | 9065c1261f8a05c6a7a2d90048c7c0665ab2896d | CVE Program |
| Linux | Linux | from 7270cc9157f474dfc46750a34c9d7defc686b2eb before 38640bc32be3fcf9526d477155bc19d3f146231f | 38640bc32be3fcf9526d477155bc19d3f146231f | CVE Program |
| Linux | Linux | 6.16 | Not documented | CVE Program |
| Microsoft | azl4 kernel 6.18.50-1.5.azl4 on Azure Linux 4.0 | Not documented | 0:6.18.57-1.1.azl4 | Microsoft MSRC |
| Linux | Linux (unaffected) | from 6.18.52 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.2.5 up to and including 7.2.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.3 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 6.16 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Advisory
Microsoft advisory published
Advisory change
Microsoft advisory revised (2.0): Information published.
Advisory change
Microsoft advisory revised (3.0): Information published.
Patch
Fix documented by Microsoft MSRC
Vendor guidance and references
- Microsoft Security Update Guide (opens in a new tab)vendor-advisory
- https://git.kernel.org/stable/c/38640bc32be3fcf9526d477155bc19d3f146231f (opens in a new tab)
- https://git.kernel.org/stable/c/5cbd8761d001c11ada73b1753d772c4745a70e72 (opens in a new tab)
- https://git.kernel.org/stable/c/9065c1261f8a05c6a7a2d90048c7c0665ab2896d (opens in a new tab)