Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 45 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 6a82582d9fa438045191074856f47165334f2777 – < 2b907001e8a83cdb71e899fd3d77ab51e2c03f10
    • affected 6a82582d9fa438045191074856f47165334f2777 – < 90e9298f2e4336a0e1ca7eeb173403df78056164
    • affected 6a82582d9fa438045191074856f47165334f2777 – < 460514d46e8892189fc933a1b4433811cfa5c309
    • affected 6a82582d9fa438045191074856f47165334f2777 – < 5aa5a1b7cc4b4bec5497ad9ef113fdfe37b232f3
    • affected 6a82582d9fa438045191074856f47165334f2777 – < a8e1f970f9040294cfd9100c681c32af6c2aeec0
    • affected 6a82582d9fa438045191074856f47165334f2777 – < d7ffbdc076675c84128d5b904e4d5167fe9f3a7f
    • affected 6a82582d9fa438045191074856f47165334f2777 – < 77832d8f1c81d9f84b6b54807fb278586001d754
    • affected 6a82582d9fa438045191074856f47165334f2777 – < bf3e39df3a397fd82967a31d17c4e02c7feab221
  • Linux · Linux

    • affected 5.13
    • unaffected < 5.13
    • unaffected 5.15.220 – ≤ 5.15.*
    • unaffected 6.1.187 – ≤ 6.1.*
    • unaffected 6.6.156 – ≤ 6.6.*
    • unaffected 6.12.108 – ≤ 6.12.*
    • unaffected 6.18.49 – ≤ 6.18.*
    • unaffected 7.1.11 – ≤ 7.1.*
    • unaffected 7.2.1 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80768 badge
[![CVE-2026-80768](https://cveledger.app/badge/CVE-2026-80768.svg)](https://cveledger.app/cve/CVE-2026-80768)

Record last updated .