CVE-2026-43483: KVM: SVM: Set/clear CR8 write interception when AVIC is (de)activated
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.11% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 01651e7751edbbc0fb4598f8367a3dabcfc8c182, 737410b32bd615b321da4fbeda490351b9af5e8b, 816fa1dfae4532e851b1fe6b2434c753ecbd86c7.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 01651e7751edbbc0fb4598f8367a3dabcfc8c182, 737410b32bd615b321da4fbeda490351b9af5e8b, 816fa1dfae4532e851b1fe6b2434c753ecbd86c7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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]
- Published
- May 13, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.7 and later · before 6.1.167
- linux linux kernel6.2 and later · before 6.6.130
- linux linux kernel6.7 and later · before 6.12.78
- linux linux kernel6.13 and later · before 6.18.19
- linux linux kernel6.19 and later · before 6.19.9
- linux linux kernel7.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.7affected
- 3bbf3565f48ce3999b5a12cde946f81bd4475312 and later · before a4123fe5d9122eef9852e4921f7cc463420f30d4affected · git
- 3bbf3565f48ce3999b5a12cde946f81bd4475312 and later · before 816fa1dfae4532e851b1fe6b2434c753ecbd86c7affected · git
- 3bbf3565f48ce3999b5a12cde946f81bd4475312 and later · before 01651e7751edbbc0fb4598f8367a3dabcfc8c182affected · git
- 3bbf3565f48ce3999b5a12cde946f81bd4475312 and later · before ba3bca40f9f25c053f69413e5f4a41dd0fd762bfaffected · git
- 3bbf3565f48ce3999b5a12cde946f81bd4475312 and later · before 737410b32bd615b321da4fbeda490351b9af5e8baffected · git
- 3bbf3565f48ce3999b5a12cde946f81bd4475312 and later · before 87d0f901a9bd8ae6be57249c737f20ac0cace93daffected · git
- before 4.7not affected · semver
- 6.1.167 and later · up to and including 6.1.*not affected · semver
- 6.6.130 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.170-1 | 6.1.170-1 |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.10-1 | 6.19.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-43477May 13, 2026 · drm/i915/vrr: Configure VRR timings after enabling TRANS_DDI_FUNC_CTL22Monitor
- ← EarlierCVE-2026-43478May 13, 2026 · ASoC: codecs: rt1011: Use component to get the dapm context in spk_mode_put22Monitor
- Later →CVE-2026-43484May 13, 2026 · mmc: core: Avoid bitfield RMW for claim/retune flags22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 01651e7751edbbc0fb4598f8367a3dabcfc8c182 | Vendor (CNA) |
| Linux Linux | 737410b32bd615b321da4fbeda490351b9af5e8b | Vendor (CNA) |
| Linux Linux | 816fa1dfae4532e851b1fe6b2434c753ecbd86c7 | Vendor (CNA) |
| Linux Linux | 87d0f901a9bd8ae6be57249c737f20ac0cace93d | Vendor (CNA) |
| Linux Linux | a4123fe5d9122eef9852e4921f7cc463420f30d4 | Vendor (CNA) |
| Linux Linux | ba3bca40f9f25c053f69413e5f4a41dd0fd762bf | Vendor (CNA) |
| debian:linux | 6.1.170-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0249 · May 15, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/737410b32bd615b321da4fbeda490351b9af5e8b
- git.kernel.org/stable/c/816fa1dfae4532e851b1fe6b2434c753ecbd86c7
- git.kernel.org/stable/c/87d0f901a9bd8ae6be57249c737f20ac0cace93d
- git.kernel.org/stable/c/a4123fe5d9122eef9852e4921f7cc463420f30d4
- git.kernel.org/stable/c/ba3bca40f9f25c053f69413e5f4a41dd0fd762bf
Vendor advisories and official records. Exploit/PoC links are deliberately left out.