Skip to main content

Linux Kernel EUVDEUVD-2026-66484

| CVE-2026-80569 HIGH
2026-08-26 Linux GHSA-3268-6g62-7794
7.8
CVSS 3.1 · Vendor: Linux
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain or compromise RMI4 device firmware
  2. Delivery
    Configure device to report inflated F55 electrode counts
  3. Exploit
    Connect device to target Linux system
  4. Execution
    Kernel allocates undersized F54 report buffer
  5. Persist
    rmi_f54_work() writes past buffer boundary
  6. Impact
    Kernel heap corruption enables privilege escalation

Vulnerability Assessment

Exploitation Conditions

Exploitation requires: (1) the target system running an unpatched Linux kernel version with the synaptics-rmi4 driver loaded (present on systems with Synaptics RMI4 touchpads, common in laptops); (2) a malicious or malfunctioning RMI4 device that reports F55 electrode counts exceeding F54 electrode counts - this requires either physical insertion of a rogue device or firmware-level compromise of an existing touchpad; (3) the F55 function being active and reporting electrode counts (i.e., drv_data->num_*_electrodes being set). On conforming, well-behaved hardware, F55 configured electrodes are a subset of F54 physical electrodes and the condition is never triggered - so production systems with legitimate hardware are not at risk unless the hardware is tampered with. Exploitation is limited to local access and requires low OS-level privileges (PR:L per CVSS), but the hardware-level prerequisite is the dominant limiting factor. Remote exploitation is not possible.

Impact

The NVD-assigned CVSS 3.1 score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) reflects high kernel-level impact with low attack complexity once a malicious device is present. However, the AC:L rating warrants scrutiny: exploiting this flaw requires either physical insertion of a rogue RMI4 device or prior compromise of the device's firmware to misreport F55 electrode counts - both are non-trivial preconditions that effectively raise practical attack complexity. EPSS data is not available for this CVE. The vulnerability is not listed in the CISA KEV catalog, and no public exploit code has been identified. SSVC signals: exploitation status is none/public, automatable is no (requires hardware interaction), technical impact is total if achieved. Real-world risk is moderate-to-elevated for affected hardware configurations (Linux laptops with Synaptics RMI4 touchpads in environments where hardware supply chain integrity is a concern) but low for general-purpose servers without this input hardware. The greatest practical risk scenario is physical access attacks in high-security environments or firmware supply chain abuse targeting specific laptop models.

Exploit ScenarioDerived

An attacker with physical access to a Linux laptop equipped with a Synaptics RMI4 touchpad replaces or reprograms the touchpad firmware to report F55 electrode counts larger than the F54 counts. When the compromised device is connected and the kernel's rmi_f54_work() runs a diagnostics scan, the inflated report_size causes the read loop to write attacker-influenced data past the end of the report_data buffer in kernel memory, enabling kernel heap corruption that could be leveraged for local privilege escalation. No public proof-of-concept exploit has been identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 27, 2026

Out-of-bounds memory write in the Linux kernel's synaptics-rmi4 input driver allows a local attacker with access to a malicious or malfunctioning RMI4 touchpad device to corrupt kernel memory, potentially enabling privilege escalation or information disclosure. The root cause is a mismatch between the F54 report buffer allocation size (derived from F54 electrode counts) and the transfer size computed from F55 electrode counts - both sourced directly from device queries with no cross-validation. Vendor patches are confirmed across multiple stable kernel branches; no public exploit or CISA KEV listing has been identified at time of analysis.

RemediationAI

The primary fix is to upgrade to a patched Linux kernel stable release: 5.10.266, 5.15.217, 6.1.184, 6.6.153, 6.12.105, 6.18.46, 7.1.10, or 7.2, as referenced in the upstream commits at https://git.kernel.org/stable/c/b3932101c9c457148038392bc977f9b31e125a86 and corresponding stable-branch commits. Distribution-specific kernel updates should be applied via the standard package manager once vendor-backported packages become available. If immediate patching is not feasible, a targeted compensating control is to blacklist or restrict loading of the hid-rmi or rmi_core kernel module on systems that do not require Synaptics RMI4 touchpad support (e.g., servers), using /etc/modprobe.d/blacklist.conf - trade-off is loss of touchpad functionality on affected hardware. On systems where the touchpad is required, enforcing hardware supply chain integrity controls (secure boot with firmware attestation) reduces the risk from rogue device insertion. Restricting physical port access (USB, I2C) on sensitive systems mitigates the hardware attack vector but has operational impact on usability.

Affected VersionsENISA

Linux patch: 5.15.217
Linux c762cc68b6a12eedebefc156ea4838e54804e2eb <b3932101c9c457148038392bc977f9b31e125a86
Linux 4.10
Linux c762cc68b6a12eedebefc156ea4838e54804e2eb <b2f596f00d27703ce09167201ba57f55be8d2f9a
Linux patch: 7.1.10
Linux patch: 7.2
Linux c762cc68b6a12eedebefc156ea4838e54804e2eb <6b3bdd44d4cd7d5e35de1d0f06d4930f3cecd403
Linux patch: 6.6.153
Linux c762cc68b6a12eedebefc156ea4838e54804e2eb <b7b9a8b1c303b62371698e396654d6724c79cb74
Linux patch: 6.12.105
Linux patch: 6.18.46
Linux patch: 5.10.266
Linux patch: 6.1.184
Linux patch: 0
Linux c762cc68b6a12eedebefc156ea4838e54804e2eb <12be3c6ca9589afd6ade41a59c761866e526634d
Linux c762cc68b6a12eedebefc156ea4838e54804e2eb <49c5adc2b7d6e43c5cf033e1c86fdb9c16ababb1
Linux c762cc68b6a12eedebefc156ea4838e54804e2eb <42eaf0e6f79c487f419737314cf0760f7331d368
Linux c762cc68b6a12eedebefc156ea4838e54804e2eb <6b06aab79ff166d5781ce792d91acc2e58b1770b

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The Synaptics RMI4 protocol is used by Synaptics touchpad devices, commonly integrated into laptops and embedded systems. The kernel driver exposes diagnostics via the F54 RMI function. The buffer for diagnostic reports (report_data) is allocated at probe time using F54's own electrode counts: array3_size(f54->num_tx_electrodes, f54->num_rx_electrodes, sizeof(u16)). However, rmi_f54_get_report_size() computes the transfer size from a separate F55 function's electrode counts (drv_data->num_*_electrodes), which are independently reported by the device and can each reach 255. Because no code constrains F55 electrode counts to be a subset of F54 counts, a device reporting inflated F55 values causes report_size to exceed the allocated buffer. The subsequent read loop (rmi_read_block) writes past report_data, and a V4L2 dequeue memcpy() can then read beyond the buffer as well - constituting both an out-of-bounds write and read in kernel space. The affected CPEs are cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:* spanning kernel versions from the introduction of the vulnerable code at commit c762cc68b6a12eedebefc156ea4838e54804e2eb (approximately Linux 4.10) through to the patched stable releases.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Linux) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.0 HIGH

AC:H reflects that exploitation requires a specially crafted or compromised RMI4 device with mismatched F55/F54 electrode counts - a non-default hardware precondition beyond normal local access.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE 6.8 MEDIUM
AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Red Hat 5.5 MEDIUM

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
CVSS changed
Aug 27, 2026 - 06:22 NVD
7.8 (HIGH)
Patch available
Aug 26, 2026 - 16:17 EUVD
CVE Published
Aug 26, 2026 - 14:37 cve.org
UNKNOWN (no severity yet)
CVE Published
Aug 26, 2026 - 14:37 cve.org
HIGH 7.8

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

Input: synaptics-rmi4 - bound the F54 report size to the allocated buffer

rmi_f54_work() reads a diagnostics report from the device into f54->report_data, sizing the transfer with rmi_f54_get_report_size():

report_size = rmi_f54_get_report_size(f54); ... for (i = 0; i < report_size; i += F54_REPORT_DATA_SIZE) { int size = min(F54_REPORT_DATA_SIZE, report_size - i); ... rmi_read_block(.., f54->report_data + i, size); }

report_data is allocated once at probe from F54's own electrode counts (array3_size(f54->num_tx_electrodes, f54->num_rx_electrodes, sizeof(u16))), but rmi_f54_get_report_size() computes the size from drv_data->num_*_electrodes when those are set, i.e. from the F55 function's electrode counts. Both counts come straight from device queries (F54 and F55 each report up to 255 electrodes) and nothing constrains the F55 counts to the F54 ones.

A malicious or malfunctioning RMI4 device that reports larger F55 electrode counts than its F54 counts makes report_size exceed the allocation, so the read loop writes past report_data (and the V4L2 dequeue memcpy() then reads past it). On conforming hardware the F55 configured electrodes are a subset of the F54 physical electrodes, so report_size never exceeds the buffer and well-behaved devices are unaffected.

Record the allocation size and reject a report that does not fit, mirroring the existing zero-size check.

Executive ViewAI

Why It Matters

The Linux kernel's Synaptics RMI4 touchpad driver contains a memory corruption vulnerability (CVE-2026-80569, CVSS 7.8) affecting systems with these input devices. Local attackers with access to affected touchpad hardware could escalate system privileges or access sensitive kernel memory; no public exploit has been identified at time of analysis. Vendor patches are available across multiple stable Linux kernel branches, requiring coordinated updates across the organization's Linux deployment base.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.1%
Top 98% exploitable
Prevalence
High
Linux kernel runs on most servers, desktops, and laptops globally
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact
High

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 16.0 Not-Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy