CVE-2026-46113: KVM: x86: Fix shadow paging use-after-free due to unexpected GFN
Noroxi assessment
Priority: Monitor (action score 35/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.19% (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 06c19c967b845b63172601fe459667d973b7e6b7, 0cb2af2ea66ad8ff195c156ea690f11216285bdf, 14d1e55dfd2cf4711bff164a6aaaddb783552134; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 06c19c967b845b63172601fe459667d973b7e6b7, 0cb2af2ea66ad8ff195c156ea690f11216285bdf, 14d1e55dfd2cf4711bff164a6aaaddb783552134; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1 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: Fix shadow paging use-after-free due to unexpected GFN The shadow MMU computes GFNs for direct shadow pages using sp->gfn plus the SPTE index. This assumption breaks for shadow paging if the guest page tables are modified between VM entries (similar to commit aad885e77496, "KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE", 2026-03-27). The flow is as follows: - a PDE is installed for a 2MB mapping, and a page in that area is accessed. KVM creates a kvm_mmu_page consisting of 512 4KB pages; the kvm_mmu_page is marked by FNAME(fetch) as direct-mapped because the guest's mapping is a huge page (and thus contiguous). - the PDE mapping is changed from outside the guest. - the guest accesses another page in the same 2MB area. KVM installs a new leaf SPTE and rmap entry; the SPTE uses the "correct" GFN (i.e. based on the new mapping, as changed in the previous step) but that GFN is outside of the [sp->gfn, sp->gfn + 511] range; therefore the rmap entry cannot be found and removed when the kvm_mmu_page is zapped. - the memslot that covers the first 2MB mapping is deleted, and the kvm_mmu_page for the now-invalid GPA is zapped. However, rmap_remove() only looks at the [sp->gfn, sp->gfn + 511] range established in step 1, and fails to find the rmap entry that was recorded by step 3. - any operation that causes an rmap walk for the same page accessed by step 3 then walks a stale rmap and dereferences a freed kvm_mmu_page. This includes dirty logging or MMU notifier invalidations (e.g., from MADV_DONTNEED). The underlying issue is that KVM's walking of shadow PTEs assumes that if a SPTE is present when KVM wants to install a non-leaf SPTE, then the existing kvm_mmu_page must be for the correct gfn. Because the only way for the gfn to be wrong is if KVM messed up and failed to zap a SPTE... which shouldn't happen, but *actually* only happens in response to a guest write. That bug dates back literally forever, as even the first version of KVM assumes that the GFN matches and walks into the "wrong" shadow page. However, that was only an imprecision until 2032a93d66fa ("KVM: MMU: Don't allocate gfns page for direct mmu pages") came along. Fix it by checking for a target gfn mismatch and zapping the existing SPTE. That way the old SP and rmap entries are gone, KVM installs the rmap in the right location, and everyone is happy.
- ALSA-2026:36956
- ALSA-2026:36957
- ALSA-2026:39082
- ALSA-2026:39083
- RHSA-2026:36956
- RHSA-2026:36957
- RHSA-2026:37729
- RHSA-2026:38902
- RHSA-2026:39082
- RHSA-2026:39083
- RHSA-2026:39371
- RHSA-2026:39983
- RHSA-2026:40082
- RHSA-2026:41229
- RHSA-2026:49033
- RLSA-2026:36956
- RLSA-2026:36957
- SUSE-SU-2026:22964-1
- SUSE-SU-2026:22965-1
- SUSE-SU-2026:22966-1
- Published
- May 28, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- CWE-416
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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 kernel2.6.20 and later · before 6.1.175
- linux linux kernel6.2 and later · before 6.6.140
- linux linux kernel6.7 and later · before 6.12.88
- linux linux kernel6.13 and later · before 6.18.30
- linux linux kernel6.19 and later · before 7.0.7
- linux linux kernel7.1
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
- 2.6.20affected
- 6aa8b732ca01c3d7a54e93f4d701b8aabbe60fb7 and later · before 9597963a8ca16259d194a1d9950d7bd22a10ab2faffected · git
- 6aa8b732ca01c3d7a54e93f4d701b8aabbe60fb7 and later · before e9d4ea13aa2b6400bb10ec64b370ba3dadcd22f0affected · git
- 6aa8b732ca01c3d7a54e93f4d701b8aabbe60fb7 and later · before 488e386484ec8c0e558be6e156edf34ed9f4d5c8affected · git
- 6aa8b732ca01c3d7a54e93f4d701b8aabbe60fb7 and later · before 06c19c967b845b63172601fe459667d973b7e6b7affected · git
- 6aa8b732ca01c3d7a54e93f4d701b8aabbe60fb7 and later · before 738ec97b1855df6c08fe2369f798fa0b972e556baffected · git
- 6aa8b732ca01c3d7a54e93f4d701b8aabbe60fb7 and later · before 14d1e55dfd2cf4711bff164a6aaaddb783552134affected · git
- 6aa8b732ca01c3d7a54e93f4d701b8aabbe60fb7 and later · before 0cb2af2ea66ad8ff195c156ea690f11216285bdfaffected · git
- before 2.6.20not affected · semver
- 5.15.222 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.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.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-46110May 28, 2026 · net: stmmac: Prevent NULL deref when RX memory exhausted30Monitor
- ← EarlierCVE-2026-46111May 28, 2026 · Bluetooth: hci_conn: fix potential UAF in create_big_sync31Monitor
- Later →CVE-2026-46114May 28, 2026 · RDMA/rxe: Reject non-8-byte ATOMIC_WRITE payloads30Monitor
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 | 06c19c967b845b63172601fe459667d973b7e6b7 | Vendor (CNA) |
| Linux Linux | 0cb2af2ea66ad8ff195c156ea690f11216285bdf | Vendor (CNA) |
| Linux Linux | 14d1e55dfd2cf4711bff164a6aaaddb783552134 | Vendor (CNA) |
| Linux Linux | 488e386484ec8c0e558be6e156edf34ed9f4d5c8 | Vendor (CNA) |
| Linux Linux | 738ec97b1855df6c08fe2369f798fa0b972e556b | Vendor (CNA) |
| Linux Linux | 9597963a8ca16259d194a1d9950d7bd22a10ab2f | Vendor (CNA) |
| Linux Linux | e9d4ea13aa2b6400bb10ec64b370ba3dadcd22f0 | Vendor (CNA) |
| azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 | 6.6.141.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:kernel | 6.12.0-211.32.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k | 6.12.0-211.32.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-core | 6.12.0-211.32.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 6.12.0-211.32.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 6.12.0-211.32.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 6.12.0-211.32.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 6.12.0-211.32.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 6.12.0-211.32.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 6.12.0-211.32.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 6.12.0-211.32.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 6.12.0-211.32.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 6.12.0-211.32.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.1.176-1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:6.12.0-211.32.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:6.12.0-211.32.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:6.12.0-211.32.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:6.12.0-211.32.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:6.12.0-211.32.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:6.12.0-211.32.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:6.12.0-211.32.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:6.12.0-211.32.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:6.12.0-211.32.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
+16
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-0290 · Jun 2, 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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
nvd-secondary
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
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/0cb2af2ea66ad8ff195c156ea690f11216285bdf
- git.kernel.org/stable/c/14d1e55dfd2cf4711bff164a6aaaddb783552134
- git.kernel.org/stable/c/488e386484ec8c0e558be6e156edf34ed9f4d5c8
- git.kernel.org/stable/c/738ec97b1855df6c08fe2369f798fa0b972e556b
- git.kernel.org/stable/c/9597963a8ca16259d194a1d9950d7bd22a10ab2f
- git.kernel.org/stable/c/e9d4ea13aa2b6400bb10ec64b370ba3dadcd22f0
- cert-portal.siemens.com/productcert/html/ssa-784472.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.