CVE-2026-89926: Linux kernel · KVM: s390: Fix length check __import_wp_info()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in fec89d327d9b2b669b5bbdac209386c6317c3722 : update Linux kernel when convenient.
Data as of 30 Oct 2026, 13:03 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in fec89d327d9b2b669b5bbdac209386c6317c3722, beb9c55af609c4c7308259d7191688c75a4e3d4a, b94ab9caa5d72c78226121cccff5e33f946da900 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 16 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A patch is available and has been applied in multiple Linux kernel commits. Users should update to a fixed kernel version containing these commits to remediate the vulnerability. Since this is a kernel-level issue, applying the official kernel update is the recommended mitigation.
Description
A vulnerability in the Linux kernel's KVM s390 module involves improper length checking in the __import_wp_info() function. The issue arises because a 64-bit length value controlled by userspace is truncated to an int for bounds checking, but the allocation uses the original 64-bit value. This discrepancy can cause allocations larger than 4GB, leading to allocation failures and kernel warnings. The flaw has been fixed in several Linux kernel commits.
References
- git.kernel.org/stable/c/36d62dfb3cac66e6a97fd850a592c2ed56e35ba5 (opens in a new tab)
- git.kernel.org/stable/c/aef540194effd768bed0bd2e6a74fe135a3d7c3a (opens in a new tab)
- git.kernel.org/stable/c/71153d3262517e1c02c3a66aa5094f279b2d1454 (opens in a new tab)
- git.kernel.org/stable/c/fec89d327d9b2b669b5bbdac209386c6317c3722 (opens in a new tab)
- git.kernel.org/stable/c/b94ab9caa5d72c78226121cccff5e33f946da900 (opens in a new tab)
- git.kernel.org/stable/c/beb9c55af609c4c7308259d7191688c75a4e3d4a (opens in a new tab)
- git.kernel.org/stable/c/3fe801db90bdeefb0bbdda42d832846b53f64f8a (opens in a new tab)
- git.kernel.org/stable/c/4c07680a467e2f7697245bcd11691bffb2a6f0ed (opens in a new tab)