Menu

Star on GitHub · 3.2k

CVE-2026-68087

In the Linux kernel, the following vulnerability has been resolved: HID: wacom: use GFP_ATOMIC in wacom_wac_queue_flush() wacom_wac_queue_flush() is called via the .raw_event callback (wacom_raw_…

Published Aug 10, 2026EPSS 0.21%

Overview

CVE-2026-68087 is a known-severity vulnerability. It was published on August 10, 2026.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

HID: wacom: use GFP_ATOMIC in wacom_wac_queue_flush()

wacom_wac_queue_flush() is called via the .raw_event callback

(wacom_raw_event → wacom_wac_pen_serial_enforce → wacom_wac_queue_flush).

For USB HID devices, this callback is invoked from hid_irq_in(), which

is a URB completion handler running in atomic context. Using GFP_KERNEL

in this path can sleep, leading to a "scheduling while atomic" bug.

Use GFP_ATOMIC instead. The existing code already handles allocation

failure by skipping the fifo entry and continuing.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-68087?

CVE-2026-68087 is a known-severity vulnerability. It was published on August 10, 2026.

How severe is CVE-2026-68087?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-68087?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-68087?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-68087 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.