CVE-2026-98201
Description
A flaw was found in the Linux kernel's input subsystem. When handling 32-bit compatibility requests for force feedback input effects, the kernel fails to properly initialize memory buffers before copying data from user space. A local user can exploit this vulnerability to read uninitialized kernel stack data, leading to information disclosure of potentially sensitive system memory.
Statement
A kernel stack information disclosure occurs in input_ff_effect_from_user() because the 32-bit compat path copies only struct ff_effect_compat into a larger native struct ff_effect. The remaining bytes retain previous kernel stack contents and input_ff_upload() stores the complete native structure in the force feedback effect table. A uinput based force feedback daemon can later receive these bytes through UI_BEGIN_FF_UPLOAD. For the CVSS the PR:L value is used because a local user or process must access the relevant input device and trigger the compat force feedback upload path. The base score uses AC:H and C:L because exploitation depends on a 32-bit compat caller, a suitable force feedback device, and a cooperating uinput based daemon, while the directly exposed data is limited to the uninitialized structure tail. The paranoid score uses AC:L and C:H when this environment is already available because repeated kernel stack disclosures may expose addresses or other sensitive values and can weaken protections such as KASLR. The issue is not network reachable. It does not provide a direct write primitive or a demonstrated standalone privilege escalation path, but the disclosed kernel data may assist exploitation of another vulnerability.
Mitigation
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 3.3 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | Low | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | None | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Understanding the Weakness (CWE)
Confidentiality,Integrity,Availability,Other
Technical Impact: Varies by Context; Read Application Data
Uninitialized variables usually contain junk, which can not be trusted for consistency. Depending on the context, uninitialized variables could lead to denial of service conditions, or modify control flow in unexpected ways. They could also contain sensitive information that could be leaked if the variable is used in output. In some cases, an attacker can "pre-initialize" the variable using previous actions - i.e., control the contents of the variable - which might enable code execution.
Availability
Technical Impact: Alter Execution Logic; Unexpected State
This can cause a race condition if a lock variable check passes when it should not.
Authorization,Other
Technical Impact: Varies by Context
Strings that are not initialized are especially dangerous, since many functions expect a null at the end -- and only at the end -- of a string.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.