Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-53359: KVM: x86: Fix shadow paging use-after-free due to unexpected role

Noroxi assessment

Priority: Monitor (action score 35/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.3% (FIRST EPSS); higher than 71.8% of all records.
  • 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 0b5e8ead71e683bcf6232db16234cf7e6d553a23, 1ae7d5a6db6c190ce183e3098ca0e0846e14d462, 2ad3afa40ac6aa340dada122f9abfa46c0a6eb35.

Low priority for now. Upgrade to Linux Linux 0b5e8ead71e683bcf6232db16234cf7e6d553a23, 1ae7d5a6db6c190ce183e3098ca0e0846e14d462, 2ad3afa40ac6aa340dada122f9abfa46c0a6eb35 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 role Commit 0cb2af2ea66ad ("KVM: x86: Fix shadow paging use-after-free due to unexpected GFN") fixed a shadow paging mismatch between stored and computed GFNs; the bug could be triggered by changing a PDE mapping from outside the guest, and then deleting a memslot. The rmap_remove() call would miss entries created after the PDE change because the GFN of the leaf SPTE does not match the GFN of the struct kvm_mmu_page. A similar hole however remains if the modified PDE points to a non-leaf page. In this case the gfn can be made to match, but the role does not match: the original large 2MB page creates a kvm_mmu_page with direct=1, while the new 4KB needs a kvm_mmu_page with direct=0. However, kvm_mmu_get_child_sp() does not compare the role, and therefore reuses the page. The next step is installing a leaf (4KB) SPTE on the new path which records an rmap entry under the gfn resolved by the walk. But when that child is zapped its parent kvm_mmu_page has direct=1 and kvm_mmu_page_get_gfn() computes the gfn for the 4KB page as sp->gfn + index instead of using sp->shadowed_translation[] (or sp->gfns[] in older kernels). It therefore fails to remove the recorded entry. When the memslot is dropped the shadow page is freed but the rmap entry survives, as in the scenario that was already fixed. Code that later walks that gfn (dirty logging, MMU notifier invalidation, and so on) dereferences an sptep that lies in the freed page, causing the use-after-free.

HighCVSS 8.8 · v3.1—Proof of concept Fix available
Published
Jul 4, 2026
Updated
Oct 3, 2026
EPSS
1.3% · 71th percentile

Report tools

JSON

Action score

35

Monitor

Low priority for now.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.3%

CISA SSVC decision

Exploitation
proof of concept
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
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-53359

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
linuxlinux 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.36 and later · before 6.1.177
  • linux linux kernel6.2 and later · before 6.6.144
  • linux linux kernel6.7 and later · before 6.12.95
  • linux linux kernel6.13 and later · before 6.18.38
  • linux linux kernel6.19 and later · before 7.1.3

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.36affected
    • 2032a93d66fa282ba0f2ea9152eeff9511fa9a96 and later · before 0b5e8ead71e683bcf6232db16234cf7e6d553a23affected · git
    • 2032a93d66fa282ba0f2ea9152eeff9511fa9a96 and later · before b1337aae5e194324e4810d561764e7793f8b3864affected · git
    • 2032a93d66fa282ba0f2ea9152eeff9511fa9a96 and later · before 9291654d69e08542de37755cebe4d5b02c3170d1affected · git
    • 2032a93d66fa282ba0f2ea9152eeff9511fa9a96 and later · before 2ad3afa40ac6aa340dada122f9abfa46c0a6eb35affected · git
    • 2032a93d66fa282ba0f2ea9152eeff9511fa9a96 and later · before 5e470998a23e4c3d89ed24e8172cb22747e61efaaffected · git
    • 2032a93d66fa282ba0f2ea9152eeff9511fa9a96 and later · before 1ae7d5a6db6c190ce183e3098ca0e0846e14d462affected · git
    • 2032a93d66fa282ba0f2ea9152eeff9511fa9a96 and later · before 81ccda30b4e83d8f5cc4fd50503c44e3a33abfebaffected · git
    • before 2.6.36not 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.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.32.1.el10_26.12.0-211.32.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.32.1.el10_26.12.0-211.32.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.32.1.el10_26.12.0-211.32.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.32.1.el10_26.12.0-211.32.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.32.1.el10_26.12.0-211.32.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.32.1.el10_26.12.0-211.32.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.32.1.el10_26.12.0-211.32.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.32.1.el10_26.12.0-211.32.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.32.1.el10_26.12.0-211.32.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.32.1.el10_26.12.0-211.32.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.32.1.el10_26.12.0-211.32.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.32.1.el10_26.12.0-211.32.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.32.1.el10_26.12.0-211.32.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.32.1.el10_26.12.0-211.32.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.32.1.el10_26.12.0-211.32.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.32.1.el10_26.12.0-211.32.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.32.1.el10_26.12.0-211.32.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.32.1.el10_26.12.0-211.32.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.32.1.el10_26.12.0-211.32.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.32.1.el10_26.12.0-211.32.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.32.1.el10_26.12.0-211.32.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.32.1.el10_26.12.0-211.32.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.32.1.el10_26.12.0-211.32.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.32.1.el10_26.12.0-211.32.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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 KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-53357Jul 2, 2026 · Bluetooth: fix UAF in l2cap_sock_cleanup_listen() vs l2cap_conn_del()
    32Monitor
  • ← EarlierCVE-2026-53358Jul 2, 2026 · Bluetooth: L2CAP: use chan timer to close channels in cleanup_listen()
    35Monitor
  • Later →CVE-2026-53360Jul 4, 2026 · KVM: SEV: Require in-GHCB scratch area if GHCB v2+ is in use
    35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0b5e8ead71e683bcf6232db16234cf7e6d553a23Vendor (CNA)
Linux Linux1ae7d5a6db6c190ce183e3098ca0e0846e14d462Vendor (CNA)
Linux Linux2ad3afa40ac6aa340dada122f9abfa46c0a6eb35Vendor (CNA)
Linux Linux5e470998a23e4c3d89ed24e8172cb22747e61efaVendor (CNA)
Linux Linux81ccda30b4e83d8f5cc4fd50503c44e3a33abfebVendor (CNA)
Linux Linux9291654d69e08542de37755cebe4d5b02c3170d1Vendor (CNA)
Linux Linuxb1337aae5e194324e4810d561764e7793f8b3864Vendor (CNA)
almalinux:kernel6.12.0-211.32.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.32.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.32.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.32.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.32.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.32.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.32.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.32.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.32.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.32.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.32.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.32.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux6.1.177-1 · Debian:12Package registry (OSV)
opensuse:kernel-source7.1.3-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-211.32.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-211.32.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-211.32.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-211.32.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-211.32.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-211.32.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-211.32.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-211.32.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-211.32.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)

+16

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×7

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02026-07-07
Proof-of-concept repository on GitHubstars:42026-07-07
Proof-of-concept repository on GitHubstars:62026-07-07
Proof-of-concept repository on GitHubstars:22026-07-07
Proof-of-concept repository on GitHubstars:02026-07-08
Proof-of-concept repository on GitHubstars:22026-07-09
Proof-of-concept repository on GitHubstars:02026-07-15

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.

  1. Published
  2. First PoC+2 d
  3. TodayNov 1, 2026+120 d
EPSS, last 120 days+1% in 7 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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.

Finders, 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
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 Free

CVSS 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.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records