CVE-2026-63916
HID: wacom: Fix OOB write in wacom_hid_set_device_mode()
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.
INFO
Published Date :
July 19, 2026, 4:17 p.m.
Last Modified :
July 27, 2026, 5:44 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
Solution
- Update the Linux kernel.
- Apply the patch for the wacom driver.
- Verify correct field indexing for HID_DG_INPUTMODE.
- Ensure bounds checks are in place.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-63916.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-63916 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-63916
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-63916 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-63916 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 20, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 19, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '5ae6e89f7409cb5d218bb728326eba9c650d9700', 'lessThan': '2add311d99646c9d235b2c44f9c169ba30f5db3a', 'versionType': 'git'}, {'status': 'affected', 'version': '5ae6e89f7409cb5d218bb728326eba9c650d9700', 'lessThan': '83bd8a5756a3c4a413ed8f6253f9eb2821e1ccaf', 'versionType': 'git'}, {'status': 'affected', 'version': '5ae6e89f7409cb5d218bb728326eba9c650d9700', 'lessThan': '5716a293fb19d382ca2336e08fd28a619a5f3c25', 'versionType': 'git'}, {'status': 'affected', 'version': '5ae6e89f7409cb5d218bb728326eba9c650d9700', 'lessThan': 'ed598de9f61582902406d352d99f2073d8e00298', 'versionType': 'git'}, {'status': 'affected', 'version': '5ae6e89f7409cb5d218bb728326eba9c650d9700', 'lessThan': '43e7c02d6090a82fd60d63491f6871aec906345e', 'versionType': 'git'}, {'status': 'affected', 'version': '5ae6e89f7409cb5d218bb728326eba9c650d9700', 'lessThan': 'b8338111e14183972359009c12d0dbd81d2e1e16', 'versionType': 'git'}, {'status': 'affected', 'version': '5ae6e89f7409cb5d218bb728326eba9c650d9700', 'lessThan': '5db3fca0cec7b33bc5379411d0a60d792c9f9bc0', 'versionType': 'git'}, {'status': 'affected', 'version': '5ae6e89f7409cb5d218bb728326eba9c650d9700', 'lessThan': 'c0a8899e02ddebd51e2589835182c239c2e224ae', 'versionType': 'git'}], 'programFiles': ['drivers/hid/wacom_sys.c', 'drivers/hid/wacom_wac.h'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '3.18'}, {'status': 'unaffected', 'version': '0', 'lessThan': '3.18', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.10.259', 'versionType': 'semver', 'lessThanOrEqual': '5.10.*'}, {'status': 'unaffected', 'version': '5.15.210', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.176', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.143', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.93', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.35', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.12', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/hid/wacom_sys.c', 'drivers/hid/wacom_wac.h'], 'defaultStatus': 'affected'}] Added 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. Added Reference https://git.kernel.org/stable/c/2add311d99646c9d235b2c44f9c169ba30f5db3a Added Reference https://git.kernel.org/stable/c/43e7c02d6090a82fd60d63491f6871aec906345e Added Reference https://git.kernel.org/stable/c/5716a293fb19d382ca2336e08fd28a619a5f3c25 Added Reference https://git.kernel.org/stable/c/5db3fca0cec7b33bc5379411d0a60d792c9f9bc0 Added Reference https://git.kernel.org/stable/c/83bd8a5756a3c4a413ed8f6253f9eb2821e1ccaf Added Reference https://git.kernel.org/stable/c/b8338111e14183972359009c12d0dbd81d2e1e16 Added Reference https://git.kernel.org/stable/c/c0a8899e02ddebd51e2589835182c239c2e224ae Added Reference https://git.kernel.org/stable/c/ed598de9f61582902406d352d99f2073d8e00298