Skip to content
Noroxi
CVE-2026-68359· NVD / CVE Program· CNA Linux

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

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().

—No exploit Fix available
Published
Aug 10, 2026
Updated
Aug 19, 2026
EPSS
0.2% · 13th percentile
CWE
—
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.17affected
    • 53e68c20aeb1e23419bed811aa3a309ceda200f9 and later · before 761249a3d92db83ae19670c4ecdf73c0a85bcb61affected · git
    • 53e68c20aeb1e23419bed811aa3a309ceda200f9 and later · before 185c0880397aee9def0af5a59ea65f22f37ad658affected · git
    • 53e68c20aeb1e23419bed811aa3a309ceda200f9 and later · before a2a15de020597efbff84b4281dd472e5860b7e3eaffected · git
    • 53e68c20aeb1e23419bed811aa3a309ceda200f9 and later · before 205cff797a94757ec88ba299c8e2bf2e1e3f4bbfaffected · git
    • 53e68c20aeb1e23419bed811aa3a309ceda200f9 and later · before 18d7c523891004226bccdba39dd681eca22ceb8aaffected · git
    • 53e68c20aeb1e23419bed811aa3a309ceda200f9 and later · before 59d104b54b0b42e30fd2a68d24ee5c49dcc54d1eaffected · git
    • before 5.17not affected · semver
    • 6.1.183 and later · up to and including 6.1.*not affected · semver
    • 6.6.148 and later · up to and including 6.6.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.187-16.1.187-1
Debian:12linux-6.12before 6.12.101-1~deb12u16.12.101-1~deb12u1
Debian:13linuxbefore 6.12.101-16.12.101-1
Debian:14linuxbefore 7.1.6-17.1.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan
  • CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler
    40Plan
  • CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index
    40Plan
  • CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux185c0880397aee9def0af5a59ea65f22f37ad658Vendor (CNA)
Linux Linux18d7c523891004226bccdba39dd681eca22ceb8aVendor (CNA)
Linux Linux205cff797a94757ec88ba299c8e2bf2e1e3f4bbfVendor (CNA)
Linux Linux59d104b54b0b42e30fd2a68d24ee5c49dcc54d1eVendor (CNA)
Linux Linux761249a3d92db83ae19670c4ecdf73c0a85bcb61Vendor (CNA)
Linux Linuxa2a15de020597efbff84b4281dd472e5860b7e3eVendor (CNA)
azl3 kernel 6.6.143.1-1 on Azure Linux 3.06.6.150.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.101-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records