Look up another CVE · open CVE-2026-68091 in the interactive tracker
CVE-2026-68091
HID: wacom: stop hardware after post-start probe failures
Published 2026-08-10 (2 months ago) by the Linux kernel CNA. Subsystem drivers/hid. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-68091 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | fixed | 6.1.180-1 | Update the kernel and reboot. Fixed in 6.1.180-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixed | 6.12.96-1 | Update the kernel and reboot. Fixed in 6.12.96-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.1.4-1 | Update the kernel and reboot. Fixed in 7.1.4-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.4-1 | Update the kernel and reboot. Fixed in 7.1.4-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
wacom_parse_and_register() starts HID hardware before registering inputs and initializing pad LEDs/remotes. Those later steps can fail, but their error paths currently release Wacom resources without stopping the HID hardware. Route post-hid_hw_start() failures through hid_hw_stop() before releasing driver resources. This issue was identified during our ongoing static-analysis research while reviewing kernel code.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/hid/wacom_sys.c
- What this is
- HID WACOM DRIVERMAINTAINERS section matched on drivers/hid/wacom_* · linux-input@vger.kernel.org · Maintained
- Kernel module
- wacom
Check it on the machine
grep -wE 'CONFIG_HID|CONFIG_HID_SUPPORT|CONFIG_HID_WACOM' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w wacomPrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.
- bookworm, trixie, forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64
- M
- a module where it is built at all; some flavours do not build it
- Build switches
- CONFIG_HID, CONFIG_HID_SUPPORT, CONFIG_HID_WACOM
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-08-10 (2 months ago)source
- CVSS
- 8.8 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- adjacent network (AV:A)source
- EPSS
- 0.26%, higher than 16.8% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/hid
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 5.10.210 | 5.10.261 | 5a7ca028facf |
| 5.15.149 | 5.15.212 | 3e6473a4f059 |
| 6.1.79 | 6.1.178 | 46d8b8c85ae0 |
| 6.6.18 | 6.6.145 | 1a1ebdcb56ae |
| 6.8 | 6.12.96 | 75eb2173b63a |
| 6.8 | 6.18.39 | 416095e9a603 |
| 6.8 | 7.1.4 | e2cc711a9df3 |
| 6.8 | 7.2 | ec2612b8ad9e |
| 4.19.307 | 0 | 0 |
| 5.4.269 | 0 | 0 |
| 6.7.6 | 0 | 0 |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:AAttack vector, adjacent network
- The flaw is in the Wacom HID driver probe path reached when a Wacom-class HID device is connected; Bluetooth Wacom tablets are widely deployed and let an adjacent attacker deliver crafted HID traffic without USB port access.
- AC:LAttack complexity, low
- A malicious or fuzzed Wacom HID device can steer probe through post-hid_hw_start() failure paths and the scheduled init_work, reliably leaving HID hardware active after driver teardown.
- PR:NPrivileges required, none
- Exploitation requires only presenting a rogue Wacom HID device over Bluetooth or USB; no prior local account, capability, or namespace privilege on the victim host is needed.
- UI:NUser interaction, none
- No victim interaction is required beyond the attacker initiating device connection; probe failure and continued HID activity occur automatically on the kernel hotplug path.
- S:UScope, unchanged
- Impact is kernel memory corruption and privilege escalation within the host kernel, not crossing a VM, container, or IOMMU security boundary.
- C:HConfidentiality impact, high
- Continued HID callbacks and delayed work after wacom_release_resources() create a use-after-free on freed driver allocations, enabling arbitrary kernel memory disclosure.
- I:HIntegrity impact, high
- The dangling hardware/workqueue activity against freed Wacom state is a heap use-after-free that can be leveraged for arbitrary kernel writes and code execution.
- A:HAvailability impact, high
- Accessing freed probe resources from still-running HID hardware or init_work can cause kernel oops, panic, or hang, producing complete system denial of service.