CVE-2026-64172
Last modified
CVE-2026-64172 is a high-severity vulnerability rated 7.1/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Disable AVIC IPI virtualization on Hygon Family 18h (erratum #1235) Hygon Family 18h CPUs are derived from AMD Family 17h (Zen1) silicon and share the same erratum #1235: hardware may read a stale IsRunning=1 bit during ICR write emulation and silently fail to generate an AVIC_IPI_FAILURE_TARGET_NOT_RUNNING VM-Exit on the sending vCPU. The absence of the VM-Exit causes KVM to miss the required wakeup of blocking target vCPUs, leading to hung vCPUs and unbounded delays in guest execution. Extend the existing AMD Family 17h erratum #1235 workaround to also cover Hygon Family 18h. With IPI virtualization disabled, KVM never sets IsRunning=1 in the Physical ID table, so every non-self IPI generates a VM-Exit and is correctly emulated.. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Disable AVIC IPI virtualization on Hygon Family 18h (erratum #1235) Hygon Family 18h CPUs are derived from AMD Family 17h (Zen1) silicon and share the same erratum #1235: hardware may read a stale IsRunning=1 bit during ICR write emulation and silently fail to generate an AVIC_IPI_FAILURE_TARGET_NOT_RUNNING VM-Exit on the sending vCPU. The absence of the VM-Exit causes KVM to miss the required wakeup of blocking target vCPUs, leading to hung vCPUs and unbounded delays in guest execution. Extend the existing AMD Family 17h erratum #1235 workaround to also cover Hygon Family 18h. With IPI virtualization disabled, KVM never sets IsRunning=1 in the Physical ID table, so every non-self IPI generates a VM-Exit and is correctly emulated.
Metrics
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.17, < 6.18.34 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.11 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64172?
How severe is CVE-2026-64172?
How do I fix CVE-2026-64172?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64167In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64168In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64169In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-6417The GLS Shipping for WooCommerce plugin for WordPress is vul…6.1
- CVE-2026-64170In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64171In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64173In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64174In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64175In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-64176In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2026-64177In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64178In the Linux kernel, the following vulnerability has been re…8.8
Are you affected by CVE-2026-64172?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
