VDB

CVE-2026-80768

CVE-2026-80768 PUBLISHED

HID: ft260: fix stack-use-after-return write in I2C read race

Reported by linux · Published September 4, 2026

In the Linux kernel, the following vulnerability has been resolved: HID: ft260: fix stack-use-after-return write in I2C read race ft260_i2c_read() points dev->read_buf at a caller-supplied buffer (often an on-stack variable), arms a completion and waits up to five seconds for the device to return the data. The HID input callback ft260_raw_event() runs in the input/IRQ path, independent of the dev->lock mutex held by the read path, and copies the device-supplied payload into dev->read_buf after a plain NULL check. These two paths share read_buf, read_idx and read_len with no serialization. If the device delays its response until the read times out, ft260_i2c_read() resets the controller, clears read_buf and returns, unwinding the stack frame the buffer lived in. A response that arrives at that moment lets ft260_raw_event() pass the NULL check and then memcpy() the device-controlled payload into the now-freed stack location, a bounded but attacker-influenced stack-use-after-return write triggerable by malicious or malfunctioning hardware. Add a dedicated spinlock that serializes every access to read_buf, read_idx and read_len. ft260_raw_event() now holds it across the NULL check, the memcpy and the index update, while the read path takes it when arming and when clearing the buffer, so the teardown can no longer slip between the check and the copy.

EPSS 0.18% · 7.3th percentile

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
LinuxLinuxd7ffbdc076675c84128d5b904e4d5167fe9f3a7f, bf3e39df3a397fd82967a31d17c4e02c7feab221, a8e1f970f9040294cfd9100c681c32af6c2aeec0, 90e9298f2e4336a0e1ca7eeb173403df78056164, 77832d8f1c81d9f84b6b54807fb278586001d754, 5aa5a1b7cc4b4bec5497ad9ef113fdfe37b232f3, 460514d46e8892189fc933a1b4433811cfa5c309, 2b907001e8a83cdb71e899fd3d77ab51e2c03f10

Risk scores

EPSS Score
0.18%
7.3th percentile

Affected products

VendorProductVersions
LinuxLinux6a82582d9fa438045191074856f47165334f2777, 6a82582d9fa438045191074856f47165334f2777, 6a82582d9fa438045191074856f47165334f2777
LinuxLinux5.13, 0, 5.15.220
LinuxLinux7.3, 0, 5.15.220
linuxlinux_kernel5.13, 5.13, 5.13

Timeline

  • Sep 4, 2026 Coalition ESS Score
  • Sep 4, 2026 CVE Published
  • Sep 5, 2026 EPSS Score (13 in total, the first dated here)
  • Oct 19, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2026-80768
vulnetix vdb fixes CVE-2026-80768

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-80768/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›