CVE-2026-63916: Linux kernel · HID: wacom: Fix OOB write in wacom_hid_set_device_mode()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 8.8 High · fixed in ed598de9f61582902406d352d99f2073d8e00298 : patch Linux kernel soon.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Total control over the software or total information disclosure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in ed598de9f61582902406d352d99f2073d8e00298, c0a8899e02ddebd51e2589835182c239c2e224ae, b8338111e14183972359009c12d0dbd81d2e1e16 +5
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Jul 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
|
Description
In the Linux kernel, the following vulnerability has been resolved: HID: wacom: Fix OOB write in wacom_hid_set_device_mode() wacom_hid_set_device_mode() currently assumes that the HID_DG_INPUTMODE usage is always located in the first field (field[0]) of the feature report. However, a device can specify HID_DG_INPUTMODE in a different field. If HID_DG_INPUTMODE is in a field other than the first one and the first field has a report_count smaller than the usage_index of HID_DG_INPUTMODE, this leads to an out-of-bounds write to r->field[0]->value. Fix this by storing the field index of HID_DG_INPUTMODE in 'struct hid_data' during feature mapping. In wacom_hid_set_device_mode(), use this stored field index to access the correct field and add bounds checks to ensure both the field index and the value index are within valid ranges before writing.
References
- git.kernel.org/stable/c/2add311d99646c9d235b2c44f9c169ba30f5db3a (opens in a new tab)
- git.kernel.org/stable/c/83bd8a5756a3c4a413ed8f6253f9eb2821e1ccaf (opens in a new tab)
- git.kernel.org/stable/c/5716a293fb19d382ca2336e08fd28a619a5f3c25 (opens in a new tab)
- git.kernel.org/stable/c/ed598de9f61582902406d352d99f2073d8e00298 (opens in a new tab)
- git.kernel.org/stable/c/43e7c02d6090a82fd60d63491f6871aec906345e (opens in a new tab)
- git.kernel.org/stable/c/b8338111e14183972359009c12d0dbd81d2e1e16 (opens in a new tab)
- git.kernel.org/stable/c/5db3fca0cec7b33bc5379411d0a60d792c9f9bc0 (opens in a new tab)
- git.kernel.org/stable/c/c0a8899e02ddebd51e2589835182c239c2e224ae (opens in a new tab)