CVE-2026-80567: Linux kernel · Input: synaptics-rmi4 – propagate F54 worker errors to V4L2 queue
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 26 Oct 2026, 12:55 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 26 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- ubuntu.com/security/CVE-2026-80567 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-80567 (opens in a new tab)
- git.kernel.org/stable/c/be56730b547737151f24357d832b04aaa93755d5 (opens in a new tab)
- git.kernel.org/stable/c/6741a8c21d98088b7f2d9f4f86a706d311ce34a2 (opens in a new tab)
- git.kernel.org/stable/c/305c24ee25b6e08ac9f4c5f697e823cc638c38da (opens in a new tab)
- git.kernel.org/stable/c/9bbd3682f8a3e064271547133c37fcb17668d860 (opens in a new tab)
- git.kernel.org/stable/c/2b0403fb7e28f65883cd03814b62c9aa9bc7f04d (opens in a new tab)
- git.kernel.org/stable/c/70f9aad3943559af6f32cb303744f35c05ce9cf1 (opens in a new tab)
- git.kernel.org/stable/c/8786d74bf50e6797b6f655eb381ef6b25451161f (opens in a new tab)
- git.kernel.org/stable/c/7d33b752e0df385b285492b74699fc73b6becdfb (opens in a new tab)