Answer in brief
CVE-2026-63916 records a Unknown severity vulnerability in HID: wacom: Fix OOB write in wacom_hid_set_device_mode(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-63916 records a Unknown severity vulnerability in HID: wacom: Fix OOB write in wacom_hid_set_device_mode(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5ae6e89f7409cb5d218bb728326eba9c650d9700 <2add311d99646c9d235b2c44f9c169ba30f5db3a || >=5ae6e89f7409cb5d218bb728326eba9c650d9700 <83bd8a5756a3c4a413ed8f6253f9eb2821e1ccaf || >=5ae6e89f7409cb5d218bb728326eba9c650d9700 <5716a293fb19d382ca2336e08fd28a619a5f3c25 || >=5ae6e89f7409cb5d218bb728326eba9c650d9700 <ed598de9f61582902406d352d99f2073d8e00298 || >=5ae6e89f7409cb5d218bb728326eba9c650d9700 <43e7c02d6090a82fd60d63491f6871aec906345e || >=5ae6e89f7409cb5d218bb728326eba9c650d9700 <b8338111e14183972359009c12d0dbd81d2e1e16 || >=5ae6e89f7409cb5d218bb728326eba9c650d9700 <5db3fca0cec7b33bc5379411d0a60d792c9f9bc0 || >=5ae6e89f7409cb5d218bb728326eba9c650d9700 <c0a8899e02ddebd51e2589835182c239c2e224ae | 2add311d99646c9d235b2c44f9c169ba30f5db3a, 83bd8a5756a3c4a413ed8f6253f9eb2821e1ccaf, 5716a293fb19d382ca2336e08fd28a619a5f3c25, ed598de9f61582902406d352d99f2073d8e00298, 43e7c02d6090a82fd60d63491f6871aec906345e, b8338111e14183972359009c12d0dbd81d2e1e16, 5db3fca0cec7b33bc5379411d0a60d792c9f9bc0, c0a8899e02ddebd51e2589835182c239c2e224ae |
| Linux/Linuxgeneric | 3.18 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5ae6e89f7409cb5d218bb728326eba9c650d9700 <2add311d99646c9d235b2c44f9c169ba30f5db3a || >=5ae6e89f7409cb5d218bb728326eba9c650d9700 <83bd8a5756a3c4a413ed8f6253f9eb2821e1ccaf || >=5ae6e89f7409cb5d218bb728326eba9c650d9700 <5716a293fb19d382ca2336e08fd28a619a5f3c25 || >=5ae6e89f7409cb5d218bb728326eba9c650d9700 <ed598de9f61582902406d352d99f2073d8e00298 || >=5ae6e89f7409cb5d218bb728326eba9c650d9700 <43e7c02d6090a82fd60d63491f6871aec906345e || >=5ae6e89f7409cb5d218bb728326eba9c650d9700 <b8338111e14183972359009c12d0dbd81d2e1e16 || >=5ae6e89f7409cb5d218bb728326eba9c650d9700 <5db3fca0cec7b33bc5379411d0a60d792c9f9bc0 || >=5ae6e89f7409cb5d218bb728326eba9c650d9700 <c0a8899e02ddebd51e2589835182c239c2e224ae | 2add311d99646c9d235b2c44f9c169ba30f5db3a, 83bd8a5756a3c4a413ed8f6253f9eb2821e1ccaf, 5716a293fb19d382ca2336e08fd28a619a5f3c25, ed598de9f61582902406d352d99f2073d8e00298, 43e7c02d6090a82fd60d63491f6871aec906345e, b8338111e14183972359009c12d0dbd81d2e1e16, 5db3fca0cec7b33bc5379411d0a60d792c9f9bc0, c0a8899e02ddebd51e2589835182c239c2e224ae |
| Linux/Linuxgeneric | 3.18 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.