CVE-2026-68359

Description

A flaw was found in the Linux kernel's hwmon (nzxt-smart2) component. A race condition exists when the hid_hw_stop() function is called without first stopping device input/output (IO). If a device probe operation fails after IO has been initiated, this race condition can lead to a use-after-free (UAF) vulnerability. This could allow a local attacker to potentially cause a system crash (denial of service) or achieve arbitrary code execution.

Statement

This vulnerability does not present a security risk to Red Hat Enterprise Linux environments because the vulnerable NZXT Smart Device V2 hardware monitoring driver is not present in supported Red Hat kernels. Upstream exploitation would require an attacker with local access to attach a specialized hardware device, or emulate one, and trigger a probe failure during device initialization. Because the underlying driver code is not built into shipped enterprise kernels, standard deployments are unaffected.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score6.4N/AN/A
Attack VectorPhysicalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredNoneN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityHighN/AN/A
Integrity ImpactHighN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.

Frequently Asked Questions

Want to get errata notifications? Sign up here.