CVE-2026-63916
Linux kernel wacom HID OOB write causing kernel memory corruption.
Is CVE-2026-63916 being exploited?
Not confirmed. CVE-2026-63916 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.35% probability of exploitation in the next 30 days.
How severe is CVE-2026-63916?
CVE-2026-63916 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-63916?
Yes. A fix has been recorded for CVE-2026-63916. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-63916 affect?
CVE-2026-63916 affects Linux kernel (wacom HID driver), Workstations/tablets with Wacom devices attached, Embedded devices using wacom_hid. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-63916?
Install kernel update with the wacom HID fix and block untrusted HID devices.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Malicious HID feature report can trigger an out-of-bounds write in kernel, causing crashes, memory corruption, or local privilege escalation.
Patch when possible
- affected>= 5ae6e89f7409cb5d218bb728326eba9c650d9700 and < 2add311d99646c9d235b2c44f9c169ba30f5db3a
- affected>= 5ae6e89f7409cb5d218bb728326eba9c650d9700 and < 83bd8a5756a3c4a413ed8f6253f9eb2821e1ccaf
- affected>= 5ae6e89f7409cb5d218bb728326eba9c650d9700 and < 5716a293fb19d382ca2336e08fd28a619a5f3c25
- affected>= 5ae6e89f7409cb5d218bb728326eba9c650d9700 and < ed598de9f61582902406d352d99f2073d8e00298
- affected>= 5ae6e89f7409cb5d218bb728326eba9c650d9700 and < 43e7c02d6090a82fd60d63491f6871aec906345e
- affected>= 5ae6e89f7409cb5d218bb728326eba9c650d9700 and < b8338111e14183972359009c12d0dbd81d2e1e16
- affected>= 5ae6e89f7409cb5d218bb728326eba9c650d9700 and < 5db3fca0cec7b33bc5379411d0a60d792c9f9bc0
- affected>= 5ae6e89f7409cb5d218bb728326eba9c650d9700 and < c0a8899e02ddebd51e2589835182c239c2e224ae
- affected3.18
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.