CVE-2026-89917

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.

CVSS

No CVSS.

References

Link	Resource
https://git.kernel.org/stable/c/38640bc32be3fcf9526d477155bc19d3f146231f
https://git.kernel.org/stable/c/5cbd8761d001c11ada73b1753d772c4745a70e72
https://git.kernel.org/stable/c/9065c1261f8a05c6a7a2d90048c7c0665ab2896d

Configurations

No configuration.

History

No history.

Information

Published : 2026-09-16 11:17

Updated : 2026-09-16 11:17

NVD link : CVE-2026-89917

Mitre link : CVE-2026-89917

CVE.ORG link : CVE-2026-89917

JSON object : View

Products Affected

No product.

CWE

No CWE.

{"id": "CVE-2026-89917", "cveTags": [], "metrics": {}, "affected": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "affectedData": [{"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "7270cc9157f474dfc46750a34c9d7defc686b2eb", "lessThan": "5cbd8761d001c11ada73b1753d772c4745a70e72", "versionType": "git"}, {"status": "affected", "version": "7270cc9157f474dfc46750a34c9d7defc686b2eb", "lessThan": "9065c1261f8a05c6a7a2d90048c7c0665ab2896d", "versionType": "git"}, {"status": "affected", "version": "7270cc9157f474dfc46750a34c9d7defc686b2eb", "lessThan": "38640bc32be3fcf9526d477155bc19d3f146231f", "versionType": "git"}], "programFiles": ["arch/arm64/kvm/nested.c"], "defaultStatus": "unaffected"}, {"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "6.16"}, {"status": "unaffected", "version": "0", "lessThan": "6.16", "versionType": "semver"}, {"status": "unaffected", "version": "6.18.52", "versionType": "semver", "lessThanOrEqual": "6.18.*"}, {"status": "unaffected", "version": "7.2.5", "versionType": "semver", "lessThanOrEqual": "7.2.*"}, {"status": "unaffected", "version": "7.3-rc1", "versionType": "original_commit_for_fix", "lessThanOrEqual": "*"}], "programFiles": ["arch/arm64/kvm/nested.c"], "defaultStatus": "affected"}]}], "published": "2026-09-16T11:17:00.763", "references": [{"url": "https://git.kernel.org/stable/c/38640bc32be3fcf9526d477155bc19d3f146231f", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/5cbd8761d001c11ada73b1753d772c4745a70e72", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/9065c1261f8a05c6a7a2d90048c7c0665ab2896d", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Received", "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: Handle VNCR TLB invalidation race with vcpu_put() VNCR unmapping\n\nWhile VNCR TLB invalidation always occurs under the MMU lock,\nvcpu_put() doesn't, while it unmaps the VNCR page.\n\nThe problem is that the invalidation evaluates vncr_tlb::cpu to\ndecide whether an unmapping needs to take place (cpu != -1) before\nperforming it. On the other hand, this_cpu_reset_vncr_fixmap()\nunconditionally unmaps if L1_VNCR_MAPPED is set.\n\nThese two obviously can race, with a TOCTOU pattern on the TLBI\npath, and a BUG_ON() on the vcpu_put() path. And the two can end-up\ncalling vncr_fixmap(-1), with extra lethal effects.\n\nMove the reset of vncr_tlb::cpu to -1 to a common function, and make\nthis update atomic so that only a single thread can reset the field\nand perform the corresponding unmap. The vcpu_put() still need to\nunconditionally unmap the current VNCR to close another ugly race.\n\nFinally, the assignment of vncr_tlb::cpu is moved to be kept in sync\nwith the actual mapping, similar to L1_VNCR_MAPPED being set."}], "lastModified": "2026-09-16T11:17:00.763", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}