Input: evdev - fix information leak in evdev_pass_values()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 6addb1d6de1968b84852f54561cc9a999909b5a9 · < bd3c4108a56de34380edab670065e86283cb3029| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Input: evdev - fix information leak in evdev_pass_values()
In evdev_pass_values(), the input_event structure is allocated on the kernel stack and populated field-by-field. However, it is never fully initialized. On architectures where struct input_event contains explicit or implicit padding (such as the 32-bit __pad field on SPARC64), these padding bytes are left uninitialized.
When this event structure is subsequently passed to the client buffer and later copied to userspace, the uninitialized padding bytes leak kernel stack memory, potentially exposing sensitive information.
Similar issues exist in __evdev_queue_syn_dropped and __pass_event.
Fix this by explicitly zeroing the entire event structure with memset() before populating its fields. This ensures all padding bytes are cleared before the data crosses the security boundary.
From the CVE record · Linux
In the Linux kernel's evdev code, input events can contain uninitialized padding bytes. When these events are copied to userspace, a local reader of the event buffer may receive kernel stack data. The input does not specify authentication requirements.
Engineers running Linux kernels with the affected evdev code should check their kernel builds; affected versions are not specified.