Input: synaptics-rmi4 - zero report size on F54 work error
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
4.9
References 8
git.kernel.org
- stable/c/62079c17ec07d64362bec367ee7a525b0dbf6bf9
- stable/c/79521ed3cc9ea48476666ccacf45ecd6954b29a4
- stable/c/c669c64ab71afa7b467c4d7e18f6a05e96b97a1f
- stable/c/77749685e55da19b187df215b5da4080842ca5c7
- stable/c/c6cfda79f26c69e97db9805808c3b44d02227b4b
- stable/c/b28593a05afdd812b590e1045b5bd862a5869225
- stable/c/88c8174d72900d77fbdf2f527d54b6ff2da876a8
- stable/c/dc76c3c8e8ad09362b8c1561f3928288c15cba2e