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

Input: synaptics-rmi4 - bound the F3A keymap to the GPIO count

rmi_f3a_initialize() takes the GPIO count from the device query register
(f3a->gpio_count = buf & RMI_F3A_GPIO_COUNT, range 0..127).
rmi_f3a_map_gpios() then allocates gpio_key_map with
min(gpio_count, TRACKSTICK_RANGE_END) == at most 6 entries, but
rmi_f3a_attention() iterates the full gpio_count and dereferences
gpio_key_map[i], and input->keycodemax is set to the full gpio_count
while input->keycode points at the 6-entry allocation.

A device that reports gpio_count > 6 therefore causes an out-of-bounds
read of gpio_key_map[] on every attention interrupt, and out-of-bounds
accesses through the input core's default keymap ioctls: EVIOCGKEYCODE
reads past the buffer (leaking adjacent slab memory to user space) and
EVIOCSKEYCODE writes a caller-controlled value past it, for any process
able to open the evdev node, since input_default_getkeycode() and
input_default_setkeycode() only bound the index against keycodemax.

Size the keymap for the full gpio_count. The mapping loop is unchanged:
it still assigns only the first min(gpio_count, TRACKSTICK_RANGE_END)
entries; the remaining slots stay KEY_RESERVED (devm_kcalloc zero-fills)
and are skipped when reporting.
Published: 2026-07-25
Score: 7.8 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The synaptics‑rmi4 input driver allocates a keymap array sized to the GPIO count reported by a touchpad device, but later accesses the array out of bounds. This out‑of‑bounds read leaks neighboring slab memory through the EVIOCGKEYCODE ioctl, and a complementary write past the end of the array is possible via EVIOCSKEYCODE for any process that can open the evdev device. The flaw therefore creates a kernel memory disclosure and a local write capability.

Affected Systems

All Linux kernel builds that compile the synaptics‑rmi4 input driver are affected when a device reports more than six GPIOs. The vulnerability exists as long as the driver is enabled and the hardware advertises a larger gpio_count, regardless of distribution or kernel configuration.

Risk and Exploitability

It is inferred that an attacker would need local access to the evdev node associated with the synaptics‑rmi4 device, which is typically granted to regular users. The EPSS score is below 1% and the vulnerability is not listed in CISA KEV, indicating a low probability of widespread exploitation. The CVSS score of 7.8 reflects moderate‑to‑high severity. The flaw exposes kernel memory through EVIOCGKEYCODE and allows writes past the keymap via EVIOCSKEYCODE, giving a local write capability. This local write capability could enable privilege escalation, but that consequence is inferred from the potential impact rather than directly stated in the description.

Generated by OpenCVE AI on August 4, 2026 at 14:48 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Install a Linux kernel that includes the patch correcting the synaptics‑rmi4 keymap allocation logic.
  • Restrict access to the synaptics‑rmi4 evdev nodes by modifying udev rules or filesystem permissions so that only privileged users can open them.
  • If an immediate kernel upgrade is not possible, unload the synaptics‑rmi4 driver or add it to the blacklist to prevent the vulnerability from being exercised until a patch is available.

Generated by OpenCVE AI on August 4, 2026 at 14:48 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4717-1 linux security update
Debian DLA Debian DLA DLA-4720-1 linux security update
Debian DLA Debian DLA DLA-4723-1 linux-6.1 security update
Debian DLA Debian DLA DLA-4724-1 linux-6.12 new package
History

Mon, 03 Aug 2026 19:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-787

Tue, 28 Jul 2026 00:15:00 +0000


Mon, 27 Jul 2026 05:15:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}


Sun, 26 Jul 2026 03:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-125
CWE-787

Sat, 25 Jul 2026 09:30:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: Input: synaptics-rmi4 - bound the F3A keymap to the GPIO count rmi_f3a_initialize() takes the GPIO count from the device query register (f3a->gpio_count = buf & RMI_F3A_GPIO_COUNT, range 0..127). rmi_f3a_map_gpios() then allocates gpio_key_map with min(gpio_count, TRACKSTICK_RANGE_END) == at most 6 entries, but rmi_f3a_attention() iterates the full gpio_count and dereferences gpio_key_map[i], and input->keycodemax is set to the full gpio_count while input->keycode points at the 6-entry allocation. A device that reports gpio_count > 6 therefore causes an out-of-bounds read of gpio_key_map[] on every attention interrupt, and out-of-bounds accesses through the input core's default keymap ioctls: EVIOCGKEYCODE reads past the buffer (leaking adjacent slab memory to user space) and EVIOCSKEYCODE writes a caller-controlled value past it, for any process able to open the evdev node, since input_default_getkeycode() and input_default_setkeycode() only bound the index against keycodemax. Size the keymap for the full gpio_count. The mapping loop is unchanged: it still assigns only the first min(gpio_count, TRACKSTICK_RANGE_END) entries; the remaining slots stay KEY_RESERVED (devm_kcalloc zero-fills) and are skipped when reporting.
Title Input: synaptics-rmi4 - bound the F3A keymap to the GPIO count
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-05T12:40:28.955Z

Reserved: 2026-07-19T15:36:31.776Z

Link: CVE-2026-64277

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Analyzed

Published: 2026-07-25T10:17:08.197

Modified: 2026-08-13T18:27:27.420

Link: CVE-2026-64277

cve-icon Redhat

Severity : Important

Publid Date: 2026-07-25T00:00:00Z

Links: CVE-2026-64277 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-04T15:00:14Z

Weaknesses