CVE-2026-23401: KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE
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.18% (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 20656cd1f243d3a154aac5dd1b823110b6906fe1, 459158151a158a6703b49f3c9de0e536d8bd553f, 695320de6eadb75aaed8be1787c4ce4c189e4c7b; azl3 kernel 6.6.130.1-3 on Azure Linux 3.0 6.6.134.1-2.
Low priority for now. Upgrade to Linux Linux 20656cd1f243d3a154aac5dd1b823110b6906fe1, 459158151a158a6703b49f3c9de0e536d8bd553f, 695320de6eadb75aaed8be1787c4ce4c189e4c7b; azl3 kernel 6.6.130.1-3 on Azure Linux 3.0 6.6.134.1-2 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: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE When installing an emulated MMIO SPTE, do so *after* dropping/zapping the existing SPTE (if it's shadow-present). While commit a54aa15c6bda3 was right about it being impossible to convert a shadow-present SPTE to an MMIO SPTE due to a _guest_ write, it failed to account for writes to guest memory that are outside the scope of KVM. E.g. if host userspace modifies a shadowed gPTE to switch from a memslot to emulted MMIO and then the guest hits a relevant page fault, KVM will install the MMIO SPTE without first zapping the shadow-present SPTE. ------------[ cut here ]------------ is_shadow_present_pte(*sptep) WARNING: arch/x86/kvm/mmu/mmu.c:484 at mark_mmio_spte+0xb2/0xc0 [kvm], CPU#0: vmx_ept_stale_r/4292 Modules linked in: kvm_intel kvm irqbypass CPU: 0 UID: 1000 PID: 4292 Comm: vmx_ept_stale_r Not tainted 7.0.0-rc2-eafebd2d2ab0-sink-vm #319 PREEMPT Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 RIP: 0010:mark_mmio_spte+0xb2/0xc0 [kvm] Call Trace: <TASK> mmu_set_spte+0x237/0x440 [kvm] ept_page_fault+0x535/0x7f0 [kvm] kvm_mmu_do_page_fault+0xee/0x1f0 [kvm] kvm_mmu_page_fault+0x8d/0x620 [kvm] vmx_handle_exit+0x18c/0x5a0 [kvm_intel] kvm_arch_vcpu_ioctl_run+0xc55/0x1c20 [kvm] kvm_vcpu_ioctl+0x2d5/0x980 [kvm] __x64_sys_ioctl+0x8a/0xd0 do_syscall_64+0xb5/0x730 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x47fa3f </TASK> ---[ end trace 0000000000000000 ]---
- BDU:2026-15600
- ALSA-2026:13577
- ALSA-2026:13578
- ALSA-2026:19568
- ALSA-2026:19569
- RHSA-2026:13577
- RHSA-2026:13578
- RHSA-2026:13932
- RHSA-2026:13936
- RHSA-2026:14137
- RHSA-2026:14230
- RHSA-2026:14339
- RHSA-2026:15883
- RHSA-2026:19521
- RHSA-2026:19568
- RHSA-2026:19569
- RHSA-2026:19875
- RHSA-2026:20593
- RHSA-2026:36530
- RHSA-2026:36531
- Published
- Apr 1, 2026
- Updated
- Jul 15, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-416
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%
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 kernel5.13.1 and later · before 5.15.203
- linux linux kernel5.16 and later · before 6.1.168
- linux linux kernel6.2 and later · before 6.6.131
- linux linux kernel6.7 and later · before 6.12.80
- linux linux kernel6.13 and later · before 6.18.21
- linux linux kernel6.19 and later · before 6.19.11
- linux linux kernel5.13
- 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
- 5.13affected
- a54aa15c6bda3ca7e2f9e040ba968a1da303e24f and later · before 20656cd1f243d3a154aac5dd1b823110b6906fe1affected · git
- a54aa15c6bda3ca7e2f9e040ba968a1da303e24f and later · before ed5909992f344a7d3f4024261e9f751d9618a27daffected · git
- a54aa15c6bda3ca7e2f9e040ba968a1da303e24f and later · before fd28c5618699180cd69619801e9ae6a5266c0a22affected · git
- a54aa15c6bda3ca7e2f9e040ba968a1da303e24f and later · before 459158151a158a6703b49f3c9de0e536d8bd553faffected · git
- a54aa15c6bda3ca7e2f9e040ba968a1da303e24f and later · before 695320de6eadb75aaed8be1787c4ce4c189e4c7baffected · git
- a54aa15c6bda3ca7e2f9e040ba968a1da303e24f and later · before bce7fe59d43531623f3e43779127bfb33804925daffected · git
- a54aa15c6bda3ca7e2f9e040ba968a1da303e24f and later · before aad885e774966e97b675dfe928da164214a71605affected · git
- before 5.13not affected · semver
- 5.15.203 and later · up to and including 5.15.*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 |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.16.1.el10_2 | 6.12.0-211.16.1.el10_2 |
+96
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-23399Mar 28, 2026 · nf_tables: nft_dynset: fix possible stateful expression memleak in error path22Monitor
- ← EarlierCVE-2026-23400Mar 29, 2026 · rust_binder: call set_notification_done() without proc lock22Monitor
- Later →CVE-2026-23402Apr 1, 2026 · KVM: x86/mmu: Only WARN in direct MMUs when overwriting shadow-present SPTE22Monitor
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 | 20656cd1f243d3a154aac5dd1b823110b6906fe1 | Vendor (CNA) |
| Linux Linux | 459158151a158a6703b49f3c9de0e536d8bd553f | Vendor (CNA) |
| Linux Linux | 695320de6eadb75aaed8be1787c4ce4c189e4c7b | Vendor (CNA) |
| Linux Linux | aad885e774966e97b675dfe928da164214a71605 | Vendor (CNA) |
| Linux Linux | bce7fe59d43531623f3e43779127bfb33804925d | Vendor (CNA) |
| Linux Linux | ed5909992f344a7d3f4024261e9f751d9618a27d | Vendor (CNA) |
| Linux Linux | fd28c5618699180cd69619801e9ae6a5266c0a22 | Vendor (CNA) |
| azl3 kernel 6.6.130.1-3 on Azure Linux 3.0 | 6.6.134.1-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:bpftool | 4.18.0-553.123.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 4.18.0-553.123.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 4.18.0-553.123.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-core | 4.18.0-553.123.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-cross-headers | 4.18.0-553.123.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug | 4.18.0-553.123.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-core | 4.18.0-553.123.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-devel | 4.18.0-553.123.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules | 4.18.0-553.123.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules-extra | 4.18.0-553.123.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-devel | 4.18.0-553.123.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-doc | 4.18.0-553.123.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.1.170-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool | 0:4.18.0-553.123.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:4.18.0-553.123.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel | 0:4.18.0-553.123.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-abi-stablelists | 0:4.18.0-553.123.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-core | 0:4.18.0-553.123.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug | 0:4.18.0-553.123.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-core | 0:4.18.0-553.123.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:4.18.0-553.123.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:4.18.0-553.123.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
+5
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).
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)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- git.kernel.org/stable/c/459158151a158a6703b49f3c9de0e536d8bd553f
- git.kernel.org/stable/c/695320de6eadb75aaed8be1787c4ce4c189e4c7b
- git.kernel.org/stable/c/aad885e774966e97b675dfe928da164214a71605
- git.kernel.org/stable/c/bce7fe59d43531623f3e43779127bfb33804925d
- git.kernel.org/stable/c/ed5909992f344a7d3f4024261e9f751d9618a27d
- git.kernel.org/stable/c/fd28c5618699180cd69619801e9ae6a5266c0a22
- access.redhat.com/errata/RHSA-2026:13577
- access.redhat.com/errata/RHSA-2026:13578
- access.redhat.com/errata/RHSA-2026:13932
- access.redhat.com/errata/RHSA-2026:13936
- access.redhat.com/errata/RHSA-2026:14137
- access.redhat.com/errata/RHSA-2026:14230
- access.redhat.com/errata/RHSA-2026:14339
- access.redhat.com/errata/RHSA-2026:15883
- access.redhat.com/errata/RHSA-2026:19521
- access.redhat.com/errata/RHSA-2026:19568
- access.redhat.com/errata/RHSA-2026:19569
- access.redhat.com/errata/RHSA-2026:19875
- access.redhat.com/errata/RHSA-2026:20593
Vendor advisories and official records. Exploit/PoC links are deliberately left out.