CVE-2026-98206: Linux kernel · Input: cyttsp5 – clamp the HID report size before memcpy
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d41a80d852f2948c6d388c520e76c0a72897f003 : patch Linux kernel soon.
Data as of 26 Oct 2026, 14:05 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in d41a80d852f2948c6d388c520e76c0a72897f003, b172c69e67bc71f71f6e3d8b3258b3dec29e42c6, 495955feb57750de4a641da13d7e51fb4d0a9764 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 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
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in the Linux kernel versions identified by the provided commit hashes. Users and administrators should update to a fixed Linux kernel version that includes these patches to mitigate the vulnerability.
Description
A vulnerability in the Linux kernel's cyttsp5 input driver involved improper handling of the HID report size before a memcpy operation. The size field, sourced from the device, was used directly as the length parameter in memcpy without clamping, potentially leading to buffer overflows. This issue has been resolved by clamping the HID report size before the memcpy call.
References
- git.kernel.org/stable/c/b172c69e67bc71f71f6e3d8b3258b3dec29e42c6 (opens in a new tab)
- git.kernel.org/stable/c/d41a80d852f2948c6d388c520e76c0a72897f003 (opens in a new tab)
- git.kernel.org/stable/c/9eb261092d4c967679fa351b7190c6d9082b07c5 (opens in a new tab)
- git.kernel.org/stable/c/495955feb57750de4a641da13d7e51fb4d0a9764 (opens in a new tab)
- git.kernel.org/stable/c/85f080fb87ed5cd3e46121be677f52c82f26a0ab (opens in a new tab)