CVE-2026-43483
Last modified
CVE-2026-43483 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Set/clear CR8 write interception when AVIC is (de)activated Explicitly set/clear CR8 write interception when AVIC is (de)activated to fix a bug where KVM leaves the interception enabled after AVIC is activated. E.g. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Set/clear CR8 write interception when AVIC is (de)activated Explicitly set/clear CR8 write interception when AVIC is (de)activated to fix a bug where KVM leaves the interception enabled after AVIC is activated. E.g. if KVM emulates INIT=>WFS while AVIC is deactivated, CR8 will remain intercepted in perpetuity. On its own, the dangling CR8 intercept is "just" a performance issue, but combined with the TPR sync bug fixed by commit d02e48830e3f ("KVM: SVM: Sync TPR from LAPIC into VMCB::V_TPR even if AVIC is active"), the danging intercept is fatal to Windows guests as the TPR seen by hardware gets wildly out of sync with reality. Note, VMX isn't affected by the bug as TPR_THRESHOLD is explicitly ignored when Virtual Interrupt Delivery is enabled, i.e. when APICv is active in KVM's world. I.e. there's no need to trigger update_cr8_intercept(), this is firmly an SVM implementation flaw/detail. WARN if KVM gets a CR8 write #VMEXIT while AVIC is active, as KVM should never enter the guest with AVIC enabled and CR8 writes intercepted. [Squash fix to avic_deactivate_vmcb. - Paolo]
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.7, < 6.1.167 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.130 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.78 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.19 | — |
| Linux | Linux Kernel | >= 6.19, < 6.19.9 | — |
| Linux | Linux Kernel | 7.0 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-43483?
How severe is CVE-2026-43483?
How do I fix CVE-2026-43483?
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-43478In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43479In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-4348The BetterDocs Pro plugin for WordPress is vulnerable to SQL…7.5
- CVE-2026-43480In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43481In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-43482In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43484In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43485In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43486In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43487In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43488In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43489In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-43483?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
