CVE-2026-89926

Unknown

Last modified

CVE-2026-89926 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: KVM: s390: Fix length check __import_wp_info() struct kvm_hw_breakpoint::len is a __u64 that is fully controlled by user space. This is then assigned to wp_info->len, which is an int.

Description

In the Linux kernel, the following vulnerability has been resolved: KVM: s390: Fix length check __import_wp_info() struct kvm_hw_breakpoint::len is a __u64 that is fully controlled by user space. This is then assigned to wp_info->len, which is an int. The bounds check is done on the truncated value while the allocation uses the untruncated one: wp_info->len = bp_data->len; [...] if (wp_info->len < 0 || wp_info->len > MAX_WP_SIZE) return -EINVAL; wp_info->old_data = kmalloc(bp_data->len, GFP_KERNEL_ACCOUNT); Use the validated value for the allocation as intended. Without this fix userspace can trigger >4GB allocations which will fail and result in a WARN due to MAX_PAGE_ORDER.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 27291e2165b6de70c476b7b675308113edd69a60, < aef540194effd768bed0bd2e6a74fe135a3d7c3a; >= 27291e2165b6de70c476b7b675308113edd69a60, < 71153d3262517e1c02c3a66aa5094f279b2d1454; >= 27291e2165b6de70c476b7b675308113edd69a60, < fec89d327d9b2b669b5bbdac209386c6317c3722; >= 27291e2165b6de70c476b7b675308113edd69a60, < b94ab9caa5d72c78226121cccff5e33f946da900; >= 27291e2165b6de70c476b7b675308113edd69a60, < beb9c55af609c4c7308259d7191688c75a4e3d4a; >= 27291e2165b6de70c476b7b675308113edd69a60, < 3fe801db90bdeefb0bbdda42d832846b53f64f8a; >= 27291e2165b6de70c476b7b675308113edd69a60, < 4c07680a467e2f7697245bcd11691bffb2a6f0ed
LinuxLinux3.16

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-89926?
In the Linux kernel, the following vulnerability has been resolved: KVM: s390: Fix length check __import_wp_info() struct kvm_hw_breakpoint::len is a __u64 that is fully controlled by user space. This is then assigned to wp_info->len, which is an int. The bounds check is done on the truncated value while the allocation uses the untruncated one: wp_info->len = bp_data->len; [...] if (wp_info->len < 0 || wp_info->len > MAX_WP_SIZE) return -EINVAL; wp_info->old_data = kmalloc(bp_data->len, GFP_KERNEL_ACCOUNT); Use the validated value for the allocation as intended. Without this fix userspace can trigger >4GB allocations which will fail and result in a WARN due to MAX_PAGE_ORDER.
How severe is CVE-2026-89926?
Severity scoring for CVE-2026-89926 is pending analysis.
How do I fix CVE-2026-89926?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-89926?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST