CVE-2026-64366
Linux kernel wacom HID driver buffer overflow leading to kernel memory corruption.
Is CVE-2026-64366 being exploited?
Not confirmed. CVE-2026-64366 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.25% probability of exploitation in the next 30 days.
How severe is CVE-2026-64366?
CVE-2026-64366 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-64366?
Yes. A fix has been recorded for CVE-2026-64366. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64366 affect?
CVE-2026-64366 affects Linux kernel (wacom HID driver), Workstations/desktops with Wacom tablets, Embedded Linux devices with wacom support, Linux distributions with affected kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64366?
Apply vendor kernel updates immediately; unplug or block untrusted Wacom/USB HID devices.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted HID reports can trigger out-of-bounds write, enabling kernel memory corruption leading to privilege escalation, arbitrary kernel code execution, or DoS.
Immediate action required
- affected>= 5e013ad206895e72d7da41bc1ae89d8cb499c3aa and < ca899a926c11a59211b764b0155d9a1cdcc32b81
- affected>= 5e013ad206895e72d7da41bc1ae89d8cb499c3aa and < 57bdd10ad50d68341f500a7b330f0d8949e510ec
- affected>= 5e013ad206895e72d7da41bc1ae89d8cb499c3aa and < 6b3014ec0e9a390ca563030b2d7689921f0daef5
- affected6.15
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.