Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-98651 Overview
CVE-2026-98651 is a NULL pointer dereference vulnerability in the Linux kernel's KVM (Kernel-based Virtual Machine) subsystem for the s390 architecture. The flaw resides in the dat_cond_set_storage_key() function, where some callers pass NULL as the oldkey parameter. When the function subsequently invokes page_cond_set_storage_key(), the NULL pointer is dereferenced and triggers a kernel crash. The issue has been resolved upstream by adding a NULL check and routing the pointer to a dummy local variable when no caller-supplied storage is provided.
Critical Impact
A NULL pointer dereference in s390 KVM storage key handling can crash the host kernel, resulting in denial of service for all virtual machines running on the affected hypervisor.
Affected Products
- Linux kernel (s390 architecture, KVM subsystem)
- Distributions shipping unpatched kernels with the vulnerable dat_cond_set_storage_key() implementation
- IBM Z and LinuxONE systems running KVM-based virtualization on unpatched kernels
Discovery Timeline
- 2026-10-18 - CVE-2026-98651 published to NVD
- 2026-10-19 - Last updated in NVD database
Technical Details for CVE-2026-98651
Vulnerability Analysis
The vulnerability is a NULL pointer dereference [CWE-476] in the s390-specific KVM dynamic address translation (DAT) code path. The function dat_cond_set_storage_key() conditionally updates the storage key associated with a guest page and optionally returns the previous key through a caller-provided oldkey pointer. Some callers do not need the previous value and pass NULL. The function forwarded this pointer directly to page_cond_set_storage_key(), which unconditionally wrote to the location, causing a kernel-mode NULL dereference.
On the s390 platform, storage keys are a hardware mechanism used to control memory access and reference tracking for guest pages. Code paths that touch these keys execute in the hypervisor's privileged context, so a NULL dereference manifests as a kernel oops and typically takes down the virtualization host.
Root Cause
The root cause is a missing input validation check on the oldkey output parameter. The helper assumed every caller would supply a valid pointer, but callers legitimately pass NULL when they do not care about the previous storage key value. The fix checks whether oldkey is NULL and, when it is, redirects writes to a stack-local dummy variable so the downstream helper always receives a valid pointer.
Attack Vector
Exploitation requires the ability to trigger the vulnerable code path on an s390 KVM host. The most likely trigger is guest or host activity that invokes KVM ioctls or memory management operations that reach dat_cond_set_storage_key() with a NULLoldkey. Successful triggering results in a kernel crash and denial of service rather than code execution or privilege escalation. The vulnerability is specific to the s390 architecture and does not affect x86, ARM, or other KVM backends.
No verified public exploitation code is available. For technical details, review the upstream fixes referenced below:
Detection Methods for CVE-2026-98651
Indicators of Compromise
- Kernel oops or panic messages referencing dat_cond_set_storage_key or page_cond_set_storage_key in dmesg or /var/log/messages.
- Unexpected KVM guest termination on s390 hosts coinciding with host kernel instability.
- Hypervisor reboots on IBM Z or LinuxONE systems without a corresponding hardware event.
Detection Strategies
- Inventory s390 KVM hosts and compare the running kernel version against the fixed commits 75867536746a and 88e22ffd1e46.
- Monitor kernel log streams for stack traces that include s390 DAT or storage key helpers.
- Correlate guest VM crashes with host kernel ring buffer events to identify host-triggered denial of service.
Monitoring Recommendations
- Forward kernel ring buffer data to a centralized logging platform and alert on NULL pointer dereference traces.
- Track hypervisor uptime and unplanned restarts on s390 KVM infrastructure.
- Enable kdump or equivalent crash dump collection on s390 hosts to capture the faulting context for triage.
How to Mitigate CVE-2026-98651
Immediate Actions Required
- Apply the upstream Linux kernel patches referenced by commits 75867536746a and 88e22ffd1e46 or install the vendor-backported update for your distribution.
- Prioritize patching s390 KVM hypervisors hosting production workloads, as a successful trigger impacts every guest on the host.
- Validate that staged kernel updates include the s390 KVM fix before deploying to IBM Z or LinuxONE fleets.
Patch Information
The fix adds a NULL check in dat_cond_set_storage_key() and assigns the pointer to a dummy local variable before calling page_cond_set_storage_key(). Patched kernels are available via the upstream stable tree. Reference the commits 75867536746a and 88e22ffd1e46 and track your distribution's security advisory channel for backported builds.
Workarounds
- No supported workaround exists other than applying the kernel patch; disable or restrict KVM workloads on affected s390 hosts if patching must be deferred.
- Limit host-level access to trusted operators to reduce the chance of inadvertently triggering the vulnerable code path.
- Maintain current crash dump and automated reboot configurations to minimize downtime should the host crash before patching completes.
# Verify current kernel on an s390 KVM host and confirm patch status
uname -r
rpm -q --changelog kernel | grep -i "dat_cond_set_storage_key" || \
dpkg-query -W -f='${Version}\n' linux-image-$(uname -r)
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

