CVE-2026-63916

HID: wacom: Fix OOB write in wacom_hid_set_device_mode()

HIGH
8.8
CVSS Score
Published: July 19, 2026 at 02:55 PM UTC
Updated: October 30, 2026 at 05:44 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.18 ≤ v < 5.10.2595.11 ≤ v < 5.15.2105.16 ≤ v < 6.1.1766.13 ≤ v < 6.18.356.19 ≤ v < 7.0.126.2 ≤ v < 6.6.1436.7 ≤ v < 6.12.933.185ae6e89f7409cb5d218bb728326eba9c650d97007.1
Vendor states this is fixed in 2add311d99646c9d235b2c44f9c169ba30f5db3a (fixed)
Vendor states this is fixed in 43e7c02d6090a82fd60d63491f6871aec906345e (fixed)
Vendor states this is fixed in 5716a293fb19d382ca2336e08fd28a619a5f3c25 (fixed)
Vendor states this is fixed in 5db3fca0cec7b33bc5379411d0a60d792c9f9bc0 (fixed)
Vendor states this is fixed in 83bd8a5756a3c4a413ed8f6253f9eb2821e1ccaf (fixed)
Vendor states this is fixed in b8338111e14183972359009c12d0dbd81d2e1e16 (fixed)
Vendor states this is fixed in c0a8899e02ddebd51e2589835182c239c2e224ae (fixed)
Vendor states this is fixed in ed598de9f61582902406d352d99f2073d8e00298 (fixed)
Vendor states this is fixed in 3.18 (unaffected)
Vendor states this is fixed in 5.10.259 (unaffected)
Vendor states this is fixed in 5.15.210 (unaffected)
Vendor states this is fixed in 6.1.176 (unaffected)
Vendor states this is fixed in 6.12.93 (unaffected)
Vendor states this is fixed in 6.18.35 (unaffected)
Vendor states this is fixed in 6.6.143 (unaffected)
Vendor states this is fixed in 7.0.12 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGHLinux
Vector?

Quick Info

StatusANALYZED
CWE
CWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card