CVE-2026-98205: Linux kernel · Input: evdev – zero absinfo before partial copy in EVIOCSABS
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e834e134a32b6a5c600fa539bb49146f617743ab : update Linux kernel when convenient.
Data as of 26 Oct 2026, 12:55 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e834e134a32b6a5c600fa539bb49146f617743ab, c0aebb57b73c7d06ad21731099afe119b113c403, af5f7130cbf39e6e12336d0b7a5f6e76e4e1526b +5
Exploitation evidence
Disclosed: evidence found.
CVE published 6 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 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 fix is available and has been applied in the Linux kernel versions identified by the fixed commit hashes. Users and administrators should update to a Linux kernel version that includes these fixes to prevent information leakage. No additional mitigation steps are indicated by the vendor advisory.
Description
A vulnerability in the Linux kernel's evdev input subsystem allows uninitialized kernel stack data to be copied to userspace via the EVIOCSABS ioctl handler. This occurs because the handler copies a user-controlled size of data into a stack structure without zeroing it first, potentially leaking stale stack bytes when userspace reads back the data with EVIOCGABS. The issue is fixed by zeroing the structure before copying user data.
References
- git.kernel.org/stable/c/c0aebb57b73c7d06ad21731099afe119b113c403 (opens in a new tab)
- git.kernel.org/stable/c/89b6ffa4bc10c436fa9aecc73be105124cd58a35 (opens in a new tab)
- git.kernel.org/stable/c/e834e134a32b6a5c600fa539bb49146f617743ab (opens in a new tab)
- git.kernel.org/stable/c/af5f7130cbf39e6e12336d0b7a5f6e76e4e1526b (opens in a new tab)
- git.kernel.org/stable/c/30b853a3d71f16bd0aa66b604bc37dd1254a19b3 (opens in a new tab)
- git.kernel.org/stable/c/71e5619db11dd6429101bd967230d0321ec5ea26 (opens in a new tab)
- git.kernel.org/stable/c/3dfe48d5307a1ba22c58231d04257737015569ca (opens in a new tab)
- git.kernel.org/stable/c/8b852965b8eaf910c314dc346967ed82c8d4f235 (opens in a new tab)