The Linux kernel driver for Wacom devices contains a flaw where the function wacom_wac_queue_flush() allocates memory using GFP_KERNEL in an interrupt/atomic context. Because GFP_KERNEL can sleep, this can trigger a "scheduling while atomic" condition, causing the kernel to block or panic. The result is a denial‑of‑service that can render the system unresponsive or cause device hangs. The flaw is a classic resource-allocation misuse and can be triggered by sending crafted HID events to the device.

All Linux kernel versions that include the unsigned wacom driver before the patch that switches GFP_KERNEL to GFP_ATOMIC are vulnerable. The vulnerability is present in existing distributions that ship the wacom HID driver without the fix, so any system running a Linux kernel that has not been updated to contain the changes at commit 27c4dad1b7917b747bf080792a527997e3147c69, 55f1ad573e34abf9a0443c34bc5a63d74edba7d7, or bbe1e55629bfaabd4b2e8125b48dd3503d74ac8b is affected. Vendor-specific builds that have not applied the upstream patch remain at risk. No specific vendor version numbers are listed in the CNA data.

The CVSS score is 5.5, the EPSS score is < 1%, and the vulnerability is not listed in the CISA KEV catalog. The flaw can be triggered by any USB HID device connected to the host, so the risk to systems with Wacom input devices is moderate to high if the attacker has physical access or can supply malicious HID data. Remote exploitation would require the ability to deliver crafted HID packets through a compromised device, which is less likely. The exploitation path is straightforward: a malicious device that sends raw HID events to the kernel invokes wacom_raw_event → wacom_wac_pen_serial_enforce → wacom_wac_queue_flush, where the wrong allocation policy triggers the scheduling error.