CVE-2026-43483
What it is
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]
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Record status
- Analyzed
Affected
- Linux Kernel < 6.1.167
- Linux Kernel < 6.6.130
- Linux Kernel < 6.12.78
- Linux Kernel < 6.18.19
- Linux Kernel < 6.19.9
- Linux Kernel 7.0
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-43483.md and follow it. Check whether this project is affected by CVE-2026-43483. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/01651e7751edbbc0fb4598f8367a3dabcfc8c182
- https://git.kernel.org/stable/c/737410b32bd615b321da4fbeda490351b9af5e8b
- https://git.kernel.org/stable/c/816fa1dfae4532e851b1fe6b2434c753ecbd86c7
- https://git.kernel.org/stable/c/87d0f901a9bd8ae6be57249c737f20ac0cace93d
- https://git.kernel.org/stable/c/a4123fe5d9122eef9852e4921f7cc463420f30d4
- https://git.kernel.org/stable/c/ba3bca40f9f25c053f69413e5f4a41dd0fd762bf
References
- https://git.kernel.org/stable/c/01651e7751edbbc0fb4598f8367a3dabcfc8c182
- https://git.kernel.org/stable/c/737410b32bd615b321da4fbeda490351b9af5e8b
- https://git.kernel.org/stable/c/816fa1dfae4532e851b1fe6b2434c753ecbd86c7
- https://git.kernel.org/stable/c/87d0f901a9bd8ae6be57249c737f20ac0cace93d
- https://git.kernel.org/stable/c/a4123fe5d9122eef9852e4921f7cc463420f30d4
- https://git.kernel.org/stable/c/ba3bca40f9f25c053f69413e5f4a41dd0fd762bf