Independent & educational platform Not a government body. No link or affiliation with any government organisation. Made for learning only. Test only systems you own or are authorised to test. Become a Partner or Sponsor → Full disclaimer

CVE-2026-43483

medium

In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Set/clear CR8 write interception when AVIC is (de)activated Explicitly set/clea…

Vendor / product: Linux — linux kernel

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]

CVSS
5.5
5.5 (CVSS v3.1)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Severity source: NVD CVSS v3.1 (nvd@nist.gov)
Timeline (UTC)
Published: 2026-05-13 16:16
Modified: 2026-11-06 16:18
NVD status: Analyzed
Last synced 1 week ago
Verified against the source API 2026-11-06 16:37 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).

Affected products

linux / linux_kernel ≥4.7 <6.1.167, ≥6.2 <6.6.130, ≥6.7 <6.12.78, ≥6.13 <6.18.19, ≥6.19 <6.19.9, 7.0

Weakness classification (CWE)

NVD-CWE-noinfo

Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.

Mitigation & advisories

Patch / mitigation: https://git.kernel.org/stable/c/01651e7751edbbc0fb4598f8367a3dabcfc8c182
Patch / mitigation: https://git.kernel.org/stable/c/737410b32bd615b321da4fbeda490351b9af5e8b
Patch / mitigation: https://git.kernel.org/stable/c/816fa1dfae4532e851b1fe6b2434c753ecbd86c7
Patch / mitigation: https://git.kernel.org/stable/c/87d0f901a9bd8ae6be57249c737f20ac0cace93d
Patch / mitigation: https://git.kernel.org/stable/c/a4123fe5d9122eef9852e4921f7cc463420f30d4
Patch / mitigation: https://git.kernel.org/stable/c/ba3bca40f9f25c053f69413e5f4a41dd0fd762bf

References

Data sources

NVD CVE API 2.0 — fetched 2026-11-06 16:37 UTC · record ↗

Learn the basics

Understanding CVEs and CVSS Scores

Related CVEs