CVE-2026-98653: Linux kernel · KVM: s390: Fix _gaccess_shadow_fault()
Source GCVE Database
Not known to be exploited : upgrade to faff4c8ff3dbec6d71b89dd281a0d17c4478fa44 or 94c43c7df46433ed4d1e18f13770b019ba977bd8 when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in faff4c8ff3dbec6d71b89dd281a0d17c4478fa44, 94c43c7df46433ed4d1e18f13770b019ba977bd8
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade Linux kernel to faff4c8ff3dbec6d71b89dd281a0d17c4478fa44 or 94c43c7df46433ed4d1e18f13770b019ba977bd8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented to address this vulnerability by modifying the _gaccess_shadow_fault() function to manually call gmap_link() when necessary. Users should apply the official Linux kernel patch that resolves this issue. Since this is a kernel-level fix, updating to the patched kernel version is the recommended remediation.
Description
A vulnerability in the Linux kernel's KVM s390 subsystem related to the _gaccess_shadow_fault() function has been resolved. The issue occurs when a nested guest memory page being shadowed is not present in the parent guest gmap, causing dat_entry_walk() to fail and erroneously propagate an error to userspace. The fix involves manually calling gmap_link() on the nested guest memory if the mapping was missing.