CVE-2026-74549
CVE CVE-2026-74549EUVD EUVD-2026-59742Published 2026-08-15T12:27:56.000ZLast changed 2026-08-19T16:38:42.000ZCVSS 7.8
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 5.10.265; patch: 5.15.216; patch: 6.18.44; 29c7cb485b321c024dedc168bcbb04451176b163 <689082a4cb166a7ae9729f7b12339e69fdad6c52; patch: 7.2; patch: 6.6.151; 29c7cb485b321c024dedc168bcbb04451176b163 <25b528816f5d83be5236dc182692369e8c9402b0; 29c7cb485b321c024dedc168bcbb04451176b163 <513d847f7a95bbdbeaaf55fb942c38992587734f; 5.4; patch: 6.1.183; 29c7cb485b321c024dedc168bcbb04451176b163 <d0b704e569ac3b8416d8e02270cdc9bf830ed395; patch: 6.12.103; patch: 0; 29c7cb485b321c024dedc168bcbb04451176b163 <0d11b2a10269ace29832f584d207ff3768f79dc5; 29c7cb485b321c024dedc168bcbb04451176b163 <4ad2972ef0e1bd1018ad7a72661a4636ed7daecc; 29c7cb485b321c024dedc168bcbb04451176b163 <1b722740ac5c2b2070f9ba922f4e0f227faf0246; patch: 7.1.8; 29c7cb485b321c024dedc168bcbb04451176b163 <4a77f1d72c6db04cbbfab0250292ac71fdea5f0a
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.