Local MMIO read and write via exception misclassification
Published Oct 21, 2024 · Updated Aug 5, 2026
Improper access control in Linux allows local users in TDX guests to read and write MMIO through crafted syscall pointers. The handle_mmio() path mistakes a userspace-triggered #VE for kernel-initiated MMIO and decodes the instruction without first confirming that its target address is in kernel space. An ordinary unprivileged guest process needs an exposed MMIO or shared mapping; successful exploitation can disclose data, alter device state, or panic the guest, but the published assessment identifies no guest-to-host escape.
Summary
What happened
Improper access control in Linux allows local users in TDX guests to read and write MMIO through crafted syscall pointers. The handle_mmio() path mistakes a userspace-triggered #VE for kernel-initiated MMIO and decodes the instruction without first confirming that its target address is in kernel space. An ordinary unprivileged guest process needs an exposed MMIO or shared mapping; successful exploitation can disclose data, alter device state, or panic the guest, but the published assessment identifies no guest-to-host escape.
The record
- CVE
- CVE-2024-47727
- Published
- Oct 21, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=31d58c4e557d46fa7f8557714250fb6f89c941ae <18ecd5b74682839e7cdafb7cd1ec106df7baa18c
- Affected versionversion=31d58c4e557d46fa7f8557714250fb6f89c941ae <25703a3c980e21548774eea8c8a87a75c5c8f58c
- Affected versionversion=31d58c4e557d46fa7f8557714250fb6f89c941ae <4c0c5dcb5471de5fc8f0a1c4980e5815339e1cee
- Affected versionversion=31d58c4e557d46fa7f8557714250fb6f89c941ae <bca2e29f7e26ce7c3522f8b324c0bd85612f68e3
- Affected versionversion=31d58c4e557d46fa7f8557714250fb6f89c941ae <d4fc4d01471528da8a9797a065982e05090e1d81
- Affected versionversion=5.19
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo