HID: ft260: fix stack-use-after-return write in I2C read race
Summary
| CVE | CVE-2026-80768 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-04 16:18:02 UTC |
| Updated | 2026-09-04 16:18:02 UTC |
| 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 6a82582d9fa438045191074856f47165334f2777 2b907001e8a83cdb71e899fd3d77ab51e2c03f10 git |
Not specified |
| CNA |
Linux |
Linux |
affected 6a82582d9fa438045191074856f47165334f2777 90e9298f2e4336a0e1ca7eeb173403df78056164 git |
Not specified |
| CNA |
Linux |
Linux |
affected 6a82582d9fa438045191074856f47165334f2777 460514d46e8892189fc933a1b4433811cfa5c309 git |
Not specified |
| CNA |
Linux |
Linux |
affected 6a82582d9fa438045191074856f47165334f2777 5aa5a1b7cc4b4bec5497ad9ef113fdfe37b232f3 git |
Not specified |
| CNA |
Linux |
Linux |
affected 6a82582d9fa438045191074856f47165334f2777 a8e1f970f9040294cfd9100c681c32af6c2aeec0 git |
Not specified |
| CNA |
Linux |
Linux |
affected 6a82582d9fa438045191074856f47165334f2777 d7ffbdc076675c84128d5b904e4d5167fe9f3a7f git |
Not specified |
| CNA |
Linux |
Linux |
affected 6a82582d9fa438045191074856f47165334f2777 77832d8f1c81d9f84b6b54807fb278586001d754 git |
Not specified |
| CNA |
Linux |
Linux |
affected 6a82582d9fa438045191074856f47165334f2777 bf3e39df3a397fd82967a31d17c4e02c7feab221 git |
Not specified |
| CNA |
Linux |
Linux |
affected 5.13 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.13 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.15.220 5.15.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.187 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.156 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.108 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.49 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1.11 7.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.1 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/2b907001e8a83cdb71e899fd3d77ab51e2c03f10 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/90e9298f2e4336a0e1ca7eeb173403df78056164 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/bf3e39df3a397fd82967a31d17c4e02c7feab221 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/77832d8f1c81d9f84b6b54807fb278586001d754 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/460514d46e8892189fc933a1b4433811cfa5c309 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/a8e1f970f9040294cfd9100c681c32af6c2aeec0 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/d7ffbdc076675c84128d5b904e4d5167fe9f3a7f |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/5aa5a1b7cc4b4bec5497ad9ef113fdfe37b232f3 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.