CVE-2026-80768: Linux Vulnerability

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

Vendor	Product	Versions
Linux	Linux	>= 6a82582d9fa438045191074856f47165334f2777, < 2b907001e8a83cdb71e899fd3d77ab51e2c03f10; >= 6a82582d9fa438045191074856f47165334f2777, < 90e9298f2e4336a0e1ca7eeb173403df78056164; >= 6a82582d9fa438045191074856f47165334f2777, < 460514d46e8892189fc933a1b4433811cfa5c309; >= 6a82582d9fa438045191074856f47165334f2777, < 5aa5a1b7cc4b4bec5497ad9ef113fdfe37b232f3; >= 6a82582d9fa438045191074856f47165334f2777, < a8e1f970f9040294cfd9100c681c32af6c2aeec0; >= 6a82582d9fa438045191074856f47165334f2777, < d7ffbdc076675c84128d5b904e4d5167fe9f3a7f; >= 6a82582d9fa438045191074856f47165334f2777, < 77832d8f1c81d9f84b6b54807fb278586001d754; >= 6a82582d9fa438045191074856f47165334f2777, < bf3e39df3a397fd82967a31d17c4e02c7feab221
Linux	Linux	5.13

References

Timeline

Published: Sep 4, 2026
Last Modified: Sep 4, 2026
Status: Received

Frequently Asked Questions

What is CVE-2026-80768?

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.

How severe is CVE-2026-80768?

Severity scoring for CVE-2026-80768 is pending analysis.

How do I fix CVE-2026-80768?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →