# CVE-2026-68091: HID: wacom: stop hardware after post-start probe failures

> A resource leak in the Linux kernel Wacom driver can cause denial of service if hardware initialization fails after startup.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-68091, DEBIAN-CVE-2026-68091, GHSA-jmfj-p2w9-43g4, UBUNTU-CVE-2026-68091

## What is CVE-2026-68091?

CVE-2026-68091 is a high-severity denial of service vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

HID: wacom: stop hardware after post-start probe failures

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.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

## Which versions are affected by CVE-2026-68091?


## How do I fix CVE-2026-68091?

Apply the vendor's patch.

## Is CVE-2026-68091 being exploited?

There is no known exploitation of CVE-2026-68091 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68091 and fix it if it is affected.

What it is: CVE-2026-68091 is a high-severity denial of service vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-68091 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68091/ (Markdown: https://insights.sbomify.com/CVE-2026-68091/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68091
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68091
- OSV: https://osv.dev/vulnerability/CVE-2026-68091

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68091/
Summaries are generated and may contain mistakes; the official description above is the record.