CVE-2026-74549

hwmon: (nct6775-core) Prevent access to unsupported weight registers

HIGH
7.8
CVSS Score
Published: August 15, 2026 at 12:27 PM UTC
Updated: August 19, 2026 at 05:21 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%

Description

In the Linux kernel, the following vulnerability has been resolved: hwmon: (nct6775-core) Prevent access to unsupported weight registers Sashiko reports: During initialization of the nct6116 chip, the driver sets data->pwm_num to 5. However, it assigns several NCT6106 register arrays (such as NCT6106_REG_WEIGHT_DUTY_STEP, NCT6106_REG_WEIGHT_TEMP_SEL, and NCT6106_REG_WEIGHT_TEMP_*) to data->REG_PWM and data->REG_WEIGHT_TEMP. These arrays only contain 3 elements. In nct6775_update_pwm(), the driver iterates up to data->pwm_num. If data->has_pwm has bits 3 or 4 set (which is structurally possible for nct6116), the loop attempts to read elements at index 3 and 4 from these 3-element arrays. This results in a global out-of-bounds read, which can be caught by KASAN. Furthermore, the driver uses these garbage out-of-bounds values as hardware register addresses for subsequent read and write operations. This leads to invalid hardware register access, potentially causing hardware misconfiguration or system crashes. The underlying problem is that the chip does support up to five fan control channels, but only the first three support weight control. Fix the problem by extending the affected weight register arrays with zeroed fields. The driver uses zeroed register addresses to determine if a register is supported or not, and skips accesses for unsupported registers.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.4 ≤ v < 5.10.2655.4 ≤ v < 5.15.2165.4 ≤ v < 6.1.1835.4 ≤ v < 6.12.1035.4 ≤ v < 6.18.445.4 ≤ v < 6.6.1515.4 ≤ v < 7.1.85.4 ≤ v < 7.229c7cb485b321c024dedc168bcbb04451176b1635.4
Vendor states this is fixed in 0d11b2a10269ace29832f584d207ff3768f79dc5 (fixed)
Vendor states this is fixed in 1b722740ac5c2b2070f9ba922f4e0f227faf0246 (fixed)
Vendor states this is fixed in 25b528816f5d83be5236dc182692369e8c9402b0 (fixed)
Vendor states this is fixed in 4a77f1d72c6db04cbbfab0250292ac71fdea5f0a (fixed)
Vendor states this is fixed in 4ad2972ef0e1bd1018ad7a72661a4636ed7daecc (fixed)
Vendor states this is fixed in 513d847f7a95bbdbeaaf55fb942c38992587734f (fixed)
Vendor states this is fixed in 689082a4cb166a7ae9729f7b12339e69fdad6c52 (fixed)
Vendor states this is fixed in d0b704e569ac3b8416d8e02270cdc9bf830ed395 (fixed)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 5.4 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.103 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 6.6.151 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card