PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-80754 Linux CVE debrief

A vulnerability was found in the Linux kernel's synaptics-rmi4 module. During F55 sensor detection, a typo led to the incorrect assignment of the transmitter electrode count, which was then used to determine diagnostics report size. This could lead to incorrect report size calculations and potential out-of-bounds buffer accesses. The issue arises from a copy-paste error in the F55 sensor detection code, where the receiver (RX) electrode count was incorrectly assigned to the transmitter (TX) electrode count. This typo was then propagated to the driver data, affecting the F54 diagnostics report size calculation. On devices with more RX than TX electrodes, this resulted in an inflated perceived TX count, leading to incorrect report size calculations and potential out-of-bounds buffer accesses. To address this vulnerability, it is essential to correct the typos and ensure accurate TX electrode count assignment.

Vendor
Linux
Product
Unknown
CVSS
HIGH 7.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-03
Original CVE updated
2026-09-04
Advisory published
2026-09-03
Advisory updated
2026-09-04

Who should care

Linux kernel developers, Linux distribution maintainers, and users of Linux-based systems, particularly those using the synaptics-rmi4 module, should review their configurations and apply patches to address the vulnerability. This includes IT teams responsible for Linux-based systems, security teams monitoring for potential vulnerabilities, and developers working with the Linux kernel.

Technical summary

The Linux kernel's synaptics-rmi4 module is vulnerable to a typo in the F55 sensor detection, leading to incorrect transmitter electrode count assignment. This could result in incorrect report size calculations and potential out-of-bounds buffer accesses. The vulnerability is caused by a copy-paste error in the F55 sensor detection code, where the receiver (RX) electrode count was incorrectly assigned to the transmitter (TX) electrode count. This typo affects the F54 diagnostics report size calculation, potentially leading to incorrect report size calculations and out-of-bounds buffer accesses on devices with more RX than TX electrodes. To mitigate this vulnerability, it is crucial to correct the typos and ensure accurate TX electrode count assignment.

Defensive priority

Apply patches to address the vulnerability in the Linux kernel's synaptics-rmi4 module.

Recommended defensive actions

  • Apply patches to address the vulnerability in the Linux kernel's synaptics-rmi4 module
  • Review and update Linux kernel configurations to ensure the synaptics-rmi4 module is properly configured
  • Monitor Linux kernel updates for future patches related to this vulnerability
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details about the vulnerability in the Linux kernel's synaptics-rmi4 module. However, the vendor and product information is not available. To verify and assess the vulnerability, defenders should review the official CVE record, NVD entry, and Linux kernel patch notes. The vulnerability involves a typo in F55 sensor detection, leading to incorrect transmitter electrode count assignment. This could result in incorrect report size calculations and potential out-of-bounds buffer accesses. Linux kernel developers, Linux distribution maintainers, and users of Linux-based systems should review their configurations and apply patches to address the vulnerability.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-80754 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-80754

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-80754 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-80754

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/0739c65e799d4a93fe573ed23255a71fcfcc5438

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/6058f0fea10f3caf63a435677358d1b8e9325114

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/6484e00d6778fdf2209cd75940bc3902b276457f

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/9759502f5cd71805923457f183ae5b9533e20c7b

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/9b184c8337c6e12df129399007735a7fbcbbcb7b

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/a6d9646e77da7cab2dff7043a8e9f75e23b836bc

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/a81cafe3c3c2f8494063385a7b0ea7ff407bf19f

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/db4e20265ebda729610ca5cf45ca9437462c3f36

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.