The kernel’s Synaptics RMI4 driver contains a flaw where the buffer queue function fails to verify the exit status of a worker thread responsible for gathering sensor data. When that thread aborts, for example due to a timeout or a register read failure, the queue logic assumes success and passes stale or uninitialized memory to userspace. As a result, applications consuming the V4L2 stream may receive corrupted or insecure data, affecting data integrity and the correctness of sensor‑based functionality.

The issue exists in any Linux system that builds the synaptics‑rmi4 driver and enables the F54 feature for device health monitoring. All kernel releases prior to the commit that introduces error checking are affected. The vulnerability applies to generic Linux kernels that include this driver; no vendor‑specific or distribution‑specific version range was provided.

Not explicitly stated in the description, but based on the kernel driver context, it appears that local access may be required to trigger the queue operation. It does not provide escalated privileges or arbitrary code execution. Because the vulnerability only influences data handed to userspace, it can lead to incorrect sensor data usage but not a broader compromise. With no EPSS information or KEV listing, the likelihood of exploitation in the wild remains uncertain, suggesting a moderate risk contingent upon exposure of the RMI4 interface.