CVE-2026-80768: Linux kernel · HID: ft260: fix stack-use-after-return write in I2C read race
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 26 Oct 2026, 12:55 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 4 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix has been implemented that adds a dedicated spinlock to serialize access to the shared buffer and related variables, preventing the race condition. Users should apply the official Linux kernel updates that include this patch to remediate the vulnerability. No additional mitigation steps are indicated.
Description
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.
References
- nvd.nist.gov/vuln/detail/CVE-2026-80768 (opens in a new tab)
- git.kernel.org/stable/c/2b907001e8a83cdb71e899fd3d77ab51e2c03f10 (opens in a new tab)
- git.kernel.org/stable/c/460514d46e8892189fc933a1b4433811cfa5c309 (opens in a new tab)
- git.kernel.org/stable/c/5aa5a1b7cc4b4bec5497ad9ef113fdfe37b232f3 (opens in a new tab)
- git.kernel.org/stable/c/77832d8f1c81d9f84b6b54807fb278586001d754 (opens in a new tab)
- git.kernel.org/stable/c/90e9298f2e4336a0e1ca7eeb173403df78056164 (opens in a new tab)
- git.kernel.org/stable/c/a8e1f970f9040294cfd9100c681c32af6c2aeec0 (opens in a new tab)
- git.kernel.org/stable/c/bf3e39df3a397fd82967a31d17c4e02c7feab221 (opens in a new tab)
- git.kernel.org/stable/c/d7ffbdc076675c84128d5b904e4d5167fe9f3a7f (opens in a new tab)
- ubuntu.com/security/CVE-2026-80768 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-80768 (opens in a new tab)
- git.kernel.org/linus/bf3e39df3a397fd82967a31d17c4e02c7feab221 (opens in a new tab)