Kernel memory corruption via wrong HID field
Published Jul 19, 2026 · Updated Jul 19, 2026
Out-of-bounds write in the Linux kernel Wacom HID driver allows physically proximate attackers to corrupt kernel memory via a crafted descriptor. wacom_hid_set_device_mode() uses the HID_DG_INPUTMODE usage index to write field[0] even when the usage belongs to another feature-report field with a larger report count. A malicious USB or spoofed Bluetooth Wacom device triggers the write during automatic probing without a host login, causing a kernel crash or enabling kernel-context code execution.
Summary
What happened
Out-of-bounds write in the Linux kernel Wacom HID driver allows physically proximate attackers to corrupt kernel memory via a crafted descriptor. wacom_hid_set_device_mode() uses the HID_DG_INPUTMODE usage index to write field[0] even when the usage belongs to another feature-report field with a larger report count. A malicious USB or spoofed Bluetooth Wacom device triggers the write during automatic probing without a host login, causing a kernel crash or enabling kernel-context code execution.
The record
- CVE
- CVE-2026-63916
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1200
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.18
- Affected versionversion=5ae6e89f7409cb5d218bb728326eba9c650d9700 <2add311d99646c9d235b2c44f9c169ba30f5db3a
- Affected versionversion=5ae6e89f7409cb5d218bb728326eba9c650d9700 <43e7c02d6090a82fd60d63491f6871aec906345e
- Affected versionversion=5ae6e89f7409cb5d218bb728326eba9c650d9700 <5716a293fb19d382ca2336e08fd28a619a5f3c25
- Affected versionversion=5ae6e89f7409cb5d218bb728326eba9c650d9700 <5db3fca0cec7b33bc5379411d0a60d792c9f9bc0
- Affected versionversion=5ae6e89f7409cb5d218bb728326eba9c650d9700 <83bd8a5756a3c4a413ed8f6253f9eb2821e1ccaf
- Affected versionversion=5ae6e89f7409cb5d218bb728326eba9c650d9700 <b8338111e14183972359009c12d0dbd81d2e1e16
- Affected versionversion=5ae6e89f7409cb5d218bb728326eba9c650d9700 <c0a8899e02ddebd51e2589835182c239c2e224ae
- Affected versionversion=5ae6e89f7409cb5d218bb728326eba9c650d9700 <ed598de9f61582902406d352d99f2073d8e00298
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo