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-98201 Overview
CVE-2026-98201 is a Linux kernel information disclosure vulnerability in the input subsystem's force feedback (FF) compat path. The function input_ff_effect_from_user() aliases the caller's native struct ff_effect to the smaller struct ff_effect_compat and copies only the compat sized prefix from userspace. The tail of the native structure is never written, leaving uninitialized on-stack bytes in place. input_ff_upload() then stores the full native structure in ff->effects[id]. A uinput-based force feedback daemon can read those bytes back through UI_BEGIN_FF_UPLOAD, exposing kernel stack memory to userspace.
Critical Impact
A local user running on a 32-bit compat ABI against a 64-bit kernel can leak kernel stack memory, potentially including pointers useful for defeating KASLR or facilitating further exploitation.
Affected Products
- Linux kernel versions containing the vulnerable input_ff_effect_from_user() compat handling
- Systems with the evdev and uinput modules enabled
- Distributions running kernels prior to the stable backport commits referenced below
Discovery Timeline
- 2026-10-06 - CVE CVE-2026-98201 published to NVD
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-98201
Vulnerability Analysis
The vulnerability is a classic uninitialized memory use leading to kernel information disclosure [CWE-908, CWE-200]. In the compat ioctl path for EVIOCSFF, evdev_do_ioctl() allocates a native struct ff_effect on the kernel stack. This stack object inherits whatever bytes were previously left by earlier function frames.
When the kernel is running a 32-bit userspace process under compat mode, input_ff_effect_from_user() casts that native structure to a smaller struct ff_effect_compat and copies only sizeof(struct ff_effect_compat) bytes from userspace. The remaining bytes of the native layout, which exist because 64-bit fields and alignment pad the native structure beyond the compat size, are never overwritten.
The fully populated native structure is subsequently stored in ff->effects[id]. A privileged-free attacker that owns a uinput device can issue UI_BEGIN_FF_UPLOAD to retrieve the stored effect, including the stale stack bytes. Repeated uploads can be used to harvest kernel memory contents over time.
Root Cause
The root cause is the missing initialization of the native struct ff_effect prior to the compat copy. The compat path assumes the structure will be fully populated by the copy_from_user() call, but the compat layout is strictly smaller than the native layout, leaving a trailing region uninitialized.
Attack Vector
Exploitation requires local access and the ability to open both an evdev input device and a uinput device. The attacker triggers the compat EVIOCSFF ioctl path and then reads the uploaded effect back through the uinput force feedback daemon interface. No special capabilities beyond standard device access are required where distributions grant unprivileged users control of input devices.
See the upstream fix commit for the exact patch that zeroes the effect buffer before the compat copy.
Detection Methods for CVE-2026-98201
Indicators of Compromise
- Unexpected userspace processes opening both /dev/input/event* and /dev/uinput concurrently
- Repeated EVIOCSFF ioctl invocations followed by UI_BEGIN_FF_UPLOAD reads from non-gaming or non-accessibility processes
- Unprivileged processes performing high-frequency force feedback uploads without any attached physical input device
Detection Strategies
- Audit ioctl syscalls targeting input and uinput devices using eBPF or auditd rules, flagging calls to EVIOCSFF and UI_BEGIN_FF_UPLOAD from unexpected binaries
- Monitor 32-bit processes running under compat mode on 64-bit kernels; the vulnerability only triggers on the compat path
- Correlate device access with process lineage to identify non-interactive workloads touching input subsystems
Monitoring Recommendations
- Enable kernel audit rules for input subsystem device opens and track uinput consumers
- Collect syscall telemetry centrally and alert on compat ioctl invocations against force feedback endpoints
- Track installed kernel package versions across the fleet to confirm backport coverage
How to Mitigate CVE-2026-98201
Immediate Actions Required
- Apply the stable kernel update that includes the fix zeroing struct ff_effect before the compat copy
- Restrict access to /dev/uinput to trusted users or groups via udev rules where force feedback daemons are not required
- Disable 32-bit compat ioctls on 64-bit kernels where not required by building with CONFIG_COMPAT=n or filtering via seccomp
Patch Information
The fix is distributed across multiple stable branches. Relevant commits include 0d05b43, 6c26681, b878720, c5e573b, ec174c2, ed0406e, ed0905f, and f84819e. Rebuild and reboot after applying the update.
Workarounds
- Unload the uinput module where force feedback daemons are not in use with modprobe -r uinput and blacklist it in /etc/modprobe.d/
- Use seccomp policies to block ioctl calls targeting UI_BEGIN_FF_UPLOAD for untrusted workloads
- Tighten udev permissions on /dev/uinput to deny access to unprivileged users
# Blacklist uinput where force feedback is not required
echo 'blacklist uinput' | sudo tee /etc/modprobe.d/blacklist-uinput.conf
sudo modprobe -r uinput
# Restrict /dev/uinput to the input group only
sudo tee /etc/udev/rules.d/90-uinput.rules <<'EOF'
KERNEL=="uinput", MODE="0660", GROUP="input"
EOF
sudo udevadm control --reload-rules && sudo udevadm trigger
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

