CVE-2026-63916
Last modified
CVE-2026-63916 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. 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.. EPSS estimates a 0.34% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 5ae6e89f7409cb5d218bb728326eba9c650d9700, < 2add311d99646c9d235b2c44f9c169ba30f5db3a; >= 5ae6e89f7409cb5d218bb728326eba9c650d9700, < 83bd8a5756a3c4a413ed8f6253f9eb2821e1ccaf; >= 5ae6e89f7409cb5d218bb728326eba9c650d9700, < 5716a293fb19d382ca2336e08fd28a619a5f3c25; >= 5ae6e89f7409cb5d218bb728326eba9c650d9700, < ed598de9f61582902406d352d99f2073d8e00298; >= 5ae6e89f7409cb5d218bb728326eba9c650d9700, < 43e7c02d6090a82fd60d63491f6871aec906345e; >= 5ae6e89f7409cb5d218bb728326eba9c650d9700, < b8338111e14183972359009c12d0dbd81d2e1e16; >= 5ae6e89f7409cb5d218bb728326eba9c650d9700, < 5db3fca0cec7b33bc5379411d0a60d792c9f9bc0; >= 5ae6e89f7409cb5d218bb728326eba9c650d9700, < c0a8899e02ddebd51e2589835182c239c2e224ae |
| Linux | Linux | 3.18 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-63916?
How severe is CVE-2026-63916?
How do I fix CVE-2026-63916?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-63910In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63911In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63912In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-63913In the Linux kernel, the following vulnerability has been re…8.2
- CVE-2026-63914In the Linux kernel, the following vulnerability has been re…7.3
- CVE-2026-63915In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-63917In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-63918In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63919In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-6392Tanium addressed an information disclosure vulnerability in …2.7
- CVE-2026-63920In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-63921In the Linux kernel, the following vulnerability has been re…8.8
Are you affected by CVE-2026-63916?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
