CVE-2026-80768: HID: ft260: fix stack-use-after-return write in I2C read race
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 2b907001e8a83cdb71e899fd3d77ab51e2c03f10, 460514d46e8892189fc933a1b4433811cfa5c309, 5aa5a1b7cc4b4bec5497ad9ef113fdfe37b232f3.
Low priority for now. Upgrade to Linux Linux 2b907001e8a83cdb71e899fd3d77ab51e2c03f10, 460514d46e8892189fc933a1b4433811cfa5c309, 5aa5a1b7cc4b4bec5497ad9ef113fdfe37b232f3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 4, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.13affected
- 6a82582d9fa438045191074856f47165334f2777 and later · before 2b907001e8a83cdb71e899fd3d77ab51e2c03f10affected · git
- 6a82582d9fa438045191074856f47165334f2777 and later · before 90e9298f2e4336a0e1ca7eeb173403df78056164affected · git
- 6a82582d9fa438045191074856f47165334f2777 and later · before 460514d46e8892189fc933a1b4433811cfa5c309affected · git
- 6a82582d9fa438045191074856f47165334f2777 and later · before 5aa5a1b7cc4b4bec5497ad9ef113fdfe37b232f3affected · git
- 6a82582d9fa438045191074856f47165334f2777 and later · before a8e1f970f9040294cfd9100c681c32af6c2aeec0affected · git
- 6a82582d9fa438045191074856f47165334f2777 and later · before d7ffbdc076675c84128d5b904e4d5167fe9f3a7faffected · git
- 6a82582d9fa438045191074856f47165334f2777 and later · before 77832d8f1c81d9f84b6b54807fb278586001d754affected · git
- 6a82582d9fa438045191074856f47165334f2777 and later · before bf3e39df3a397fd82967a31d17c4e02c7feab221affected · git
- before 5.13not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.1.12-1 | 7.1.12-1 |
| openSUSE:Tumbleweed | kernel-source | before 7.2.5-1.1 | 7.2.5-1.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80766Sep 4, 2026 · HID: uclogic: fix use-after-free of inrange_timer on remove0Monitor
- ← EarlierCVE-2026-80767Sep 4, 2026 · HID: sensor: custom: Fix use-after-free in enable_sensor0Monitor
- Later →CVE-2026-80769Sep 4, 2026 · HID: rapoo: fix missing hid_is_usb() check0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2b907001e8a83cdb71e899fd3d77ab51e2c03f10 | Vendor (CNA) |
| Linux Linux | 460514d46e8892189fc933a1b4433811cfa5c309 | Vendor (CNA) |
| Linux Linux | 5aa5a1b7cc4b4bec5497ad9ef113fdfe37b232f3 | Vendor (CNA) |
| Linux Linux | 77832d8f1c81d9f84b6b54807fb278586001d754 | Vendor (CNA) |
| Linux Linux | 90e9298f2e4336a0e1ca7eeb173403df78056164 | Vendor (CNA) |
| Linux Linux | a8e1f970f9040294cfd9100c681c32af6c2aeec0 | Vendor (CNA) |
| Linux Linux | bf3e39df3a397fd82967a31d17c4e02c7feab221 | Vendor (CNA) |
| Linux Linux | d7ffbdc076675c84128d5b904e4d5167fe9f3a7f | Vendor (CNA) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:kernel-source | 7.2.5-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/460514d46e8892189fc933a1b4433811cfa5c309
- git.kernel.org/stable/c/5aa5a1b7cc4b4bec5497ad9ef113fdfe37b232f3
- git.kernel.org/stable/c/77832d8f1c81d9f84b6b54807fb278586001d754
- git.kernel.org/stable/c/90e9298f2e4336a0e1ca7eeb173403df78056164
- git.kernel.org/stable/c/a8e1f970f9040294cfd9100c681c32af6c2aeec0
- git.kernel.org/stable/c/bf3e39df3a397fd82967a31d17c4e02c7feab221
- git.kernel.org/stable/c/d7ffbdc076675c84128d5b904e4d5167fe9f3a7f
Vendor advisories and official records. Exploit/PoC links are deliberately left out.