In the Linux kernel, the following vulnerability has been resolved: HID: wacom: Fix OOB write in wacom_hid_set_device_mode()… (CVE-2026-63916)
A vulnerability in the Linux kernel's wacom HID driver (wacom_hid_set_device_mode) allowed an out-of-bounds write due to incorrect assumptions about the location of HID_DG_INPUTMODE usage in feature report fields. This could lead to memory corruption when the usage is not in the first field and the first field's report_count is smaller than the usage_index. The issue has been fixed by correctly storing and using the field index and adding bounds checks before writing.
AI Analysis
Technical Summary
The Linux kernel's wacom HID driver function wacom_hid_set_device_mode assumed that the HID_DG_INPUTMODE usage was always in the first field of the feature report. However, some devices specify this usage in other fields. When HID_DG_INPUTMODE is in a different field and the first field's report_count is smaller than the usage_index, this caused an out-of-bounds write to the first field's value array. The fix involves storing the correct field index during feature mapping and adding bounds checks to ensure safe access before writing.
Potential Impact
This vulnerability could lead to an out-of-bounds write in kernel memory, potentially causing system instability or enabling privilege escalation if exploited. However, no known exploits are reported in the wild at this time.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this vulnerability by correcting the field indexing and adding bounds checks. Users should apply the official Linux kernel updates that include this patch once available. Patch status is not yet confirmed; check the vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: HID: wacom: Fix OOB write in wacom_hid_set_device_mode()… (CVE-2026-63916)
Description
A vulnerability in the Linux kernel's wacom HID driver (wacom_hid_set_device_mode) allowed an out-of-bounds write due to incorrect assumptions about the location of HID_DG_INPUTMODE usage in feature report fields. This could lead to memory corruption when the usage is not in the first field and the first field's report_count is smaller than the usage_index. The issue has been fixed by correctly storing and using the field index and adding bounds checks before writing.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's wacom HID driver function wacom_hid_set_device_mode assumed that the HID_DG_INPUTMODE usage was always in the first field of the feature report. However, some devices specify this usage in other fields. When HID_DG_INPUTMODE is in a different field and the first field's report_count is smaller than the usage_index, this caused an out-of-bounds write to the first field's value array. The fix involves storing the correct field index during feature mapping and adding bounds checks to ensure safe access before writing.
Potential Impact
This vulnerability could lead to an out-of-bounds write in kernel memory, potentially causing system instability or enabling privilege escalation if exploited. However, no known exploits are reported in the wild at this time.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this vulnerability by correcting the field indexing and adding bounds checks. Users should apply the official Linux kernel updates that include this patch once available. Patch status is not yet confirmed; check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-r9m8-7m9v-6473
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-63916"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27ab2a4a8d598912f59f
Added to database: 07/19/2026, 19:38:19 UTC
Last enriched: 07/19/2026, 20:08:53 UTC
Last updated: 07/20/2026, 17:26:47 UTC
Views: 12
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.