# CVE-2026-80567: Input: synaptics-rmi4 - propagate F54 worker errors to V4L2 queue

> A local attacker can read uninitialized kernel memory via the Synaptics RMI4 driver due to ignored worker errors, potentially exposing sensitive data.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** AZL-97805, BELL-CVE-2026-80567, DEBIAN-CVE-2026-80567, UBUNTU-CVE-2026-80567

## What is CVE-2026-80567?

CVE-2026-80567 is a vulnerability in Linux, published on 26 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-80567?


## How do I fix CVE-2026-80567?

Apply the vendor's patch.

## Is CVE-2026-80567 being exploited?

There is no known exploitation of CVE-2026-80567 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80567 and fix it if it is affected.

What it is: CVE-2026-80567 is a vulnerability in Linux, published on 26 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80567 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80567/ (Markdown: https://insights.sbomify.com/CVE-2026-80567/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80567
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80567
- OSV: https://osv.dev/vulnerability/CVE-2026-80567

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80567/
Summaries are generated and may contain mistakes; the official description above is the record.