Input: synaptics-rmi4 - propagate F54 worker errors to V4L2 queue
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d · < 70f9aad3943559af6f32cb303744f35c05ce9cf1| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Input: synaptics-rmi4 - propagate F54 worker errors to V4L2 queue
Previously, rmi_f54_buffer_queue() waited for the worker thread to finish but ignored whether it succeeded. If the worker failed (e.g., due to a timeout or register read failure), the queue thread would silently return success, delivering stale or uninitialized memory to userspace.
Add a 'report_error' field to struct f54_data to store the worker's exit status. Check this field in rmi_f54_buffer_queue() after the worker finishes, and mark the buffer as VB2_BUF_STATE_ERROR if an error occurred.
From the CVE record · Linux
The Linux kernel’s synaptics-rmi4 F54 queue can report success after its worker fails, potentially delivering stale or uninitialized memory to userspace. This occurs when the worker encounters an error, such as a timeout or register read failure; authentication requirements and user interaction are not specified.
Engineers running Linux kernels with the synaptics-rmi4 F54 component should check their builds; affected versions are not specified.