Skip to main content
VulnerabilityPublished Updated

CVE-2026-63916: Linux kernel · HID: wacom: Fix OOB write in wacom_hid_set_device_mode()

Affects Linux kernelSource CVE Database V5

0

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

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 5ae6e89f7409cb5d218bb728326eba9c650d9700, < ed598de9f61582902406d352d99f2073d8e00298
Fixed in
  • ed598de9f61582902406d352d99f2073d8e00298
LinuxLinuxAffected
  • ≥ 5ae6e89f7409cb5d218bb728326eba9c650d9700, < c0a8899e02ddebd51e2589835182c239c2e224ae
Fixed in
  • c0a8899e02ddebd51e2589835182c239c2e224ae
LinuxLinuxAffected
  • ≥ 5ae6e89f7409cb5d218bb728326eba9c650d9700, < b8338111e14183972359009c12d0dbd81d2e1e16
Fixed in
  • b8338111e14183972359009c12d0dbd81d2e1e16
LinuxLinuxAffected
  • ≥ 5ae6e89f7409cb5d218bb728326eba9c650d9700, < 5716a293fb19d382ca2336e08fd28a619a5f3c25
Fixed in
  • 5716a293fb19d382ca2336e08fd28a619a5f3c25
LinuxLinuxAffected
  • ≥ 5ae6e89f7409cb5d218bb728326eba9c650d9700, < 83bd8a5756a3c4a413ed8f6253f9eb2821e1ccaf
Fixed in
  • 83bd8a5756a3c4a413ed8f6253f9eb2821e1ccaf
LinuxLinuxAffected
  • ≥ 5ae6e89f7409cb5d218bb728326eba9c650d9700, < 43e7c02d6090a82fd60d63491f6871aec906345e
Fixed in
  • 43e7c02d6090a82fd60d63491f6871aec906345e

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

Community reviews

Loading reviews…