# CVE-2026-80754: Input: synaptics-rmi4 - fix F55 transmitter electrode count typo

> A typo in the Synaptics RMI4 driver causes incorrect buffer size calculations, potentially leading to out-of-bounds memory access and system instability.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 3 Sep 2026
- **Updated:** 16 Oct 2026
- **Also known as:** AZL-99032, BELL-CVE-2026-80754, DEBIAN-CVE-2026-80754, GHSA-v4rj-p772-hjqg, UBUNTU-CVE-2026-80754

## What is CVE-2026-80754?

CVE-2026-80754 is a high-severity memory corruption vulnerability in Linux, published on 3 Sep 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 - fix F55 transmitter electrode count typo

During F55 sensor detection, the transmitter (TX) electrode count was
incorrectly assigned the value of the receiver (RX) electrode count
due to copy-paste typos.

This incorrect value was then propagated to the driver data and used
by F54 to determine the diagnostics report size. On devices with more
RX than TX electrodes, this inflated the perceived TX count, leading
to incorrect report size calculations and potential out-of-bounds
buffer accesses.

Fix the typos by correctly assigning the TX electrode counts.

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


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

Apply the vendor's patch.

## Is CVE-2026-80754 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80754 is a high-severity memory corruption vulnerability in Linux, published on 3 Sep 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-80754 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-80754/ (Markdown: https://insights.sbomify.com/CVE-2026-80754/index.md)
```

## Sources

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

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