CVE-2026-74549

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

State
Published
Severity
7.8 High
Published
Aug 15, 2026
Updated
Aug 19, 2026
Reserved
Aug 15, 2026

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.17.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 29c7cb485b321c024dedc168bcbb04451176b163 to before 0d11b2a10269ace29832f584d207ff3768f79dc5Affected
  • 29c7cb485b321c024dedc168bcbb04451176b163 to before 4a77f1d72c6db04cbbfab0250292ac71fdea5f0aAffected
  • 29c7cb485b321c024dedc168bcbb04451176b163 to before 513d847f7a95bbdbeaaf55fb942c38992587734fAffected
  • 29c7cb485b321c024dedc168bcbb04451176b163 to before 25b528816f5d83be5236dc182692369e8c9402b0Affected
  • 29c7cb485b321c024dedc168bcbb04451176b163 to before 689082a4cb166a7ae9729f7b12339e69fdad6c52Affected
  • 29c7cb485b321c024dedc168bcbb04451176b163 to before 1b722740ac5c2b2070f9ba922f4e0f227faf0246Affected
  • 29c7cb485b321c024dedc168bcbb04451176b163 to before 4ad2972ef0e1bd1018ad7a72661a4636ed7daeccAffected
  • 29c7cb485b321c024dedc168bcbb04451176b163 to before d0b704e569ac3b8416d8e02270cdc9bf830ed395Affected
LinuxLinux
  • 5.4Affected
  • before 5.4Not affected
  • 5.10.265 through 5.10.*Not affected
  • 5.15.216 through 5.15.*Not affected
  • 6.1.183 through 6.1.*Not affected
  • 6.6.151 through 6.6.*Not affected
  • 6.12.103 through 6.12.*Not affected
  • 6.18.44 through 6.18.*Not affected
  • 7.1.8 through 7.1.*Not affected
  • 7.2 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.