# CVE-2026-68359: hwmon: (nzxt-smart2) Stop device IO before calling hid_hw_stop

> A race condition in the nzxt-smart2 kernel driver allows local attackers to trigger a use-after-free, potentially leading to code execution or privilege escalation.

- **Severity:** Not scored
- **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 Aug 2026
- **Also known as:** BELL-CVE-2026-68359, DEBIAN-CVE-2026-68359, GHSA-g646-6rxh-xh86, UBUNTU-CVE-2026-68359

## What is CVE-2026-68359?

CVE-2026-68359 is an use after free 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:

hwmon: (nzxt-smart2) Stop device IO before calling hid_hw_stop

Calling hid_hw_stop() does not stop the device IO.
This results in a race condition between hid_input_report() and the point
immediately following the execution of hid_device_io_start() within
the driver probe function. If the probe operation fails after "io start"
has been initiated, this race condition will result in a UAF vulnerability.

Fix the problem by calling hid_device_io_stop() before calling
hid_hw_stop().

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


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

Apply the vendor's patch.

## Is CVE-2026-68359 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68359 is an use after free 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-68359 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-68359/ (Markdown: https://insights.sbomify.com/CVE-2026-68359/index.md)
```

## Sources

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

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