CVE-2026-80567 — Input: synaptics-rmi4 - propagate F54 worker errors to V4L2 queue
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d and < 305c24ee25b6e08ac9f4c5f697e823cc638c38da≥ 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d and < 7d33b752e0df385b285492b74699fc73b6becdfb≥ 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d and < be56730b547737151f24357d832b04aaa93755d5≥ 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d and < 2b0403fb7e28f65883cd03814b62c9aa9bc7f04d≥ 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d and < 6741a8c21d98088b7f2d9f4f86a706d311ce34a2≥ 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d and < 70f9aad3943559af6f32cb303744f35c05ce9cf1≥ 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d and < 9bbd3682f8a3e064271547133c37fcb17668d860≥ 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d and < 8786d74bf50e6797b6f655eb381ef6b25451161f and 1 moreversion 4.9 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 27, 2026 · 12 reading(s) · max 0.17%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/9bbd3682f8a3e064271547133c37fcb17668d860
- git.kernel.org/stable/c/8786d74bf50e6797b6f655eb381ef6b25451161f
- git.kernel.org/stable/c/70f9aad3943559af6f32cb303744f35c05ce9cf1
- git.kernel.org/stable/c/7d33b752e0df385b285492b74699fc73b6becdfb
- git.kernel.org/stable/c/2b0403fb7e28f65883cd03814b62c9aa9bc7f04d
- git.kernel.org/stable/c/be56730b547737151f24357d832b04aaa93755d5
- git.kernel.org/stable/c/305c24ee25b6e08ac9f4c5f697e823cc638c38da
- git.kernel.org/stable/c/6741a8c21d98088b7f2d9f4f86a706d311ce34a2
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99100 wifi: p54: validate firmware record lengths 5h
- Unknown CVE-2026-99092 riscv: patch: fix handling of bpf-jit execmem addresses 1d
- Unknown CVE-2026-99093 mm: don't schedule deferred kernel page table freeing while booting 1d
- Unknown CVE-2026-99095 drm/vc4: drain the hangcheck timer and works on V3D unbind 1d
- Unknown CVE-2026-99096 io_uring/register: don't exempt disabled rings from task restrictions 1d
- Unknown CVE-2026-99097 tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper() 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-80567 is "Input: synaptics-rmi4 - propagate F54 worker errors to V4L2 queue", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.