High [CVE-2026-98466] Transfer the hyp stack pages out of the host stage-2
This high-severity Red Hat Linux advisory covers CVE-2026-98466; related products: Red Hat Enterprise Linux 9, Red Hat OpenShift Container Platform 4, Red Hat package: kernel-rt.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Get an email when Red Hat Linux publishes the next one.
VulniPulse checks Red Hat Linux's security advisories around the clock and emails you new ones with the severity, the fixed version and the vendor's link. First month free, then US$15/month; we email you before the first charge.
Summary
Transfer the hyp stack pages out of the host stage-2. Red Hat rates this important (CVSS 8.2).
Weakness: CWE-653.
Affected products named by the advisory: Red Hat Enterprise Linux 9; Red Hat OpenShift Container Platform 4; Red Hat package: kernel-rt.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.
Official advisory · high-confidence parse· fetched 9 days ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists. Confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 9 days ago·verify at source
Mitigation checklist
- --- CME Mitigation Guidance (2026-10-20) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to revoke host stage-2 page-table mappings for per-CPU hypervisor stack memory during protected nVHE initialization: upgrade to Linux kernel 6.18.55, 7.2.9, 7.3 (or the fixed Kernel/Kernel Rt/Openshift/Ose Rhel Coreos/Kpatch builds), which walk each per-CPU hypervisor stack virtual address range using the ownership-transition walker to transfer pages out of host stage-2, closing all 2 injection vectors (host stage-2 hypervisor stack memory read, host stage-2 hypervisor stack memory modification). Until patched, this is only a concern on ARM64 Linux systems running protected KVM (pKVM / protected nVHE) mode — Non-ARM64 architectures and deployments without protected KVM mode enabled are unaffected — so Strictly limit root access and prevent privileged userspace processes from reading physical memory or interacting with debugging interfaces on the host. As a compensating measure, Enforce SELinux in enforcing mode to prevent privileged processes from accessing raw physical memory interfaces or debugging utilities capable of reading hypervisor stack pages and Enable Kernel Lockdown Mode to restrict privileged host userspace from reading or writing raw physical memory via /dev/mem and patching running kernel memory. These controls limit blast radius and contain exploitation, but they do not fix the underlying hypervisor stack memory isolation defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-301 SELinux (Enforcing Mode) (medium)
Official advisory · high-confidence parse· fetched 9 days ago·verify at source
More Red Hat Linux advisories
- CVE-2026-111497Oct 22, 2026Out-of-Bounds Write in Google Brotli Decoder
- CVE-2026-109619Oct 21, 2026fatal error handling retains stale request state leading to use-after-free
- CVE-2026-109618Oct 21, 2026OOM bailout during request parsing leads to memory corruption and RCE
- CVE-2026-97229Oct 13, 2026integer overflow issue in CI/CD regular expression compiler
- CVE-2026-64849Aug 17, 2026Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed
- CVE-2026-53362Jul 4, 2026account for fraggap on the paged allocation path
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.