Write-tracking bypass via stale SMM MMIO entries
Published Oct 23, 2026 · Updated Oct 23, 2026
Write-tracking bypass in Linux x86 KVM allows guest OS users to write RAM without invalidating cached translations via stale MMIO entries. The vcpu_cache_mmio_info() and vcpu_match_mmio_gen() helpers use the normal address-space generation even in System Management Mode (SMM), leaving obsolete SMM entries valid. After an SMM memslot update and return to normal execution, a RAM write misclassified as MMIO bypasses write tracking; nested EPT backing pages retain stale shadow translations, without a demonstrated host escape.
Summary
What happened
Write-tracking bypass in Linux x86 KVM allows guest OS users to write RAM without invalidating cached translations via stale MMIO entries. The vcpu_cache_mmio_info() and vcpu_match_mmio_gen() helpers use the normal address-space generation even in System Management Mode (SMM), leaving obsolete SMM entries valid. After an SMM memslot update and return to normal execution, a RAM write misclassified as MMIO bypasses write tracking; nested EPT backing pages retain stale shadow translations, without a demonstrated host escape.
The record
- CVE
- CVE-2026-99082
- Published
- Oct 23, 2026
- Updated
- Oct 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 23, 2026CVE publishedPublication date reported by the CVE source.
- Oct 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.2
- Affected versionversion=699023e239658e62da6f42f47d31b54788521ec1 <2566780c684c9c21241d409d790087c73070f312
- Affected versionversion=699023e239658e62da6f42f47d31b54788521ec1 <7fd4e64f4bbc8c35ae8f0d2a1fb5b77a76d5b4fd
- Affected versionversion=699023e239658e62da6f42f47d31b54788521ec1 <a63f79d9da9468952396af73e1e53330845cf876
- Affected versionversion=699023e239658e62da6f42f47d31b54788521ec1 <b3e6212dea2e4328a841ceb37f377583176dc735
- Affected versionversion=699023e239658e62da6f42f47d31b54788521ec1 <e792a9ace39d2812a5b342a1987186c7bc653204
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us