CVE-2026-43483KVM: SVM: Set/clear CR8 write interception when AVIC is (de)activated
- 5.5MediumCVSS base score
- 0.11%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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]
Timeline
ID reserved
By Linux
- 12 days later
· 12 days later
Published
- 6 months later
· 6 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.11% · top 98% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 3bbf3565f48ce3999b5a12cde946f81bd4475312 – < a4123fe5d9122eef9852e4921f7cc463420f30d4
- affected 3bbf3565f48ce3999b5a12cde946f81bd4475312 – < 816fa1dfae4532e851b1fe6b2434c753ecbd86c7
- affected 3bbf3565f48ce3999b5a12cde946f81bd4475312 – < 01651e7751edbbc0fb4598f8367a3dabcfc8c182
- affected 3bbf3565f48ce3999b5a12cde946f81bd4475312 – < ba3bca40f9f25c053f69413e5f4a41dd0fd762bf
- affected 3bbf3565f48ce3999b5a12cde946f81bd4475312 – < 737410b32bd615b321da4fbeda490351b9af5e8b
- affected 3bbf3565f48ce3999b5a12cde946f81bd4475312 – < 87d0f901a9bd8ae6be57249c737f20ac0cace93d
- affected 4.7
- unaffected < 4.7
- unaffected 6.1.167 – ≤ 6.1.*
- unaffected 6.6.130 – ≤ 6.6.*
- unaffected 6.12.78 – ≤ 6.12.*
- unaffected 6.18.19 – ≤ 6.18.*
- unaffected 6.19.9 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References6
- https://git.kernel.org/stable/c/a4123fe5d9122eef9852e4921f7cc463420f30d4 (opens in a new tab)
- https://git.kernel.org/stable/c/816fa1dfae4532e851b1fe6b2434c753ecbd86c7 (opens in a new tab)
- https://git.kernel.org/stable/c/01651e7751edbbc0fb4598f8367a3dabcfc8c182 (opens in a new tab)
- https://git.kernel.org/stable/c/ba3bca40f9f25c053f69413e5f4a41dd0fd762bf (opens in a new tab)
- https://git.kernel.org/stable/c/737410b32bd615b321da4fbeda490351b9af5e8b (opens in a new tab)
- https://git.kernel.org/stable/c/87d0f901a9bd8ae6be57249c737f20ac0cace93d (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-30019 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-43483)Record last updated .