Signal is active with 2 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD description
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.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
AVAILABLE
Momentum
STABLE
| Date | Total | Labels |
|---|
| 2026-08-26 | 1 | General1 |
| 2026-08-28 | 2 | Patch2 |
CVE-2026-80567 Linux Kernel Synaptics RMI4 Vulnerability Leads to Stale Data Delivery https://vulmon.com/vulnerabilitydetails?qid=CVE-2026-80567
Post summary
The source supplies only the CVE ID and a link to a vulnerability page with no further technical or exploit information.
🚨*CVE* CVE-2026-80567 In the Linux kernel, the following vulnerability has been resolved: Input: synaptics-rmi4 - propagate F54 worker errors to V4L2 queue Previously, rmi_f54_buffer_que… https://www.cve.org/CVERecord?id=CVE-2026-80567 ----- Traducción: CVE-2026-80567 En … https://infoflow.cloud`
Post summary
The CVE-2026-80567 in the Linux kernel has been resolved with a patch, and technical details of the issue are provided, but no PoC, exploit, or active exploitation is mentioned.
CVE-2026-80567 In the Linux kernel, the following vulnerability has been resolved: Input: synaptics-rmi4 - propagate F54 worker errors to V4L2 queue Previously, rmi_f54_buffer_que… https://www.cve.org/CVERecord?id=CVE-2026-80567
Post summary
CVE-2026-80567 was resolved in the Linux kernel with an unspecified patch addressing a worker‑error propagation issue in synaptics‑rmi4; no PoC, exploit tool, or active exploitation details are provided.