Input: synaptics-rmi4 - zero report size on F54 work error
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d · < b28593a05afdd812b590e1045b5bd862a5869225| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Input: synaptics-rmi4 - zero report size on F54 work error
In rmi_f54_work(), if an error occurs during report request or command verification, the code jumped directly to the 'error' label, bypassing the 'abort' label where f54->report_size was normally zeroed out.
This left f54->report_size containing its previous successful payload size. If a user then altered the V4L2 format to a smaller size, and a subsequent run failed, rmi_f54_buffer_queue() would copy the stale, larger payload size into the shrunken V4L2 buffer, causing a heap buffer overflow.
Fix this by merging the 'abort' and 'error' labels into a single 'out' exit path, and ensuring that f54->report_size is always set to 0 on failure by checking for error and zeroing the local report_size first.
From the CVE record · Linux
The Linux kernel’s synaptics-rmi4 F54 code can retain a stale report size after a report request or command verification fails. If a user then changes the V4L2 format to a smaller size and a subsequent run fails, the code can copy a larger payload into the smaller buffer, causing a heap buffer overflow.
Engineers running Linux kernels with the synaptics-rmi4 F54 code should check their systems; affected versions were not specified.