CVE-2026-63916High· 8.8▾ TwilightIn 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 f…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 48.4 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 16.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.4%
Last analysed / modified upstream
0.4% → 0.4%
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.
Linux >= 5ae6e89f7409cb5d218bb728326eba9c650d9700 < 2add311d99646c9d235b2c44f9c169ba30f5db3aLinux >= 5ae6e89f7409cb5d218bb728326eba9c650d9700 < 83bd8a5756a3c4a413ed8f6253f9eb2821e1ccafLinux >= 5ae6e89f7409cb5d218bb728326eba9c650d9700 < 5716a293fb19d382ca2336e08fd28a619a5f3c25Linux >= 5ae6e89f7409cb5d218bb728326eba9c650d9700 < ed598de9f61582902406d352d99f2073d8e00298Linux >= 5ae6e89f7409cb5d218bb728326eba9c650d9700 < 43e7c02d6090a82fd60d63491f6871aec906345eLinux >= 5ae6e89f7409cb5d218bb728326eba9c650d9700 < b8338111e14183972359009c12d0dbd81d2e1e16Linux >= 5ae6e89f7409cb5d218bb728326eba9c650d9700 < 5db3fca0cec7b33bc5379411d0a60d792c9f9bc0Linux >= 5ae6e89f7409cb5d218bb728326eba9c650d9700 < c0a8899e02ddebd51e2589835182c239c2e224aeLinux 3.18Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets