In the Linux kernel, the following vulnerability has been resolved:
Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count
rmif30mapgpios() allocates gpioledkeymap with min(gpioledcount, TRACKSTICKRANGEEND) == at most 6 entries, but rmif30attention() iterates the full f30->gpioledcount (device query register, range 0..31) and dereferences gpioledkeymap[i], and input->keycodemax is set to the full gpioledcount while input->keycode points at the 6-entry allocation.
A device that reports gpioled_count > 6 with GPIO support enabled therefore causes an out-of-bounds read on the attention interrupt and out-of-bounds read/write through the EVIOCGKEYCODE/EVIOCSKEYCODE ioctls, which bound the index only against keycodemax. This is the same defect as the F3A handler, which was copied from F30.
Size the keymap for the full gpioledcount; the mapping loop still assigns only the first min(gpioledcount, TRACKSTICKRANGEEND) entries.
{
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/64xxx/CVE-2026-64276.json",
"cna_assigner": "Linux"
}