Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 4 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-74549, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 29c7cb485b321c024dedc168bcbb04451176b163 – < 0d11b2a10269ace29832f584d207ff3768f79dc5
    • affected 29c7cb485b321c024dedc168bcbb04451176b163 – < 4a77f1d72c6db04cbbfab0250292ac71fdea5f0a
    • affected 29c7cb485b321c024dedc168bcbb04451176b163 – < 513d847f7a95bbdbeaaf55fb942c38992587734f
    • affected 29c7cb485b321c024dedc168bcbb04451176b163 – < 25b528816f5d83be5236dc182692369e8c9402b0
    • affected 29c7cb485b321c024dedc168bcbb04451176b163 – < 689082a4cb166a7ae9729f7b12339e69fdad6c52
    • affected 29c7cb485b321c024dedc168bcbb04451176b163 – < 1b722740ac5c2b2070f9ba922f4e0f227faf0246
    • affected 29c7cb485b321c024dedc168bcbb04451176b163 – < 4ad2972ef0e1bd1018ad7a72661a4636ed7daecc
    • affected 29c7cb485b321c024dedc168bcbb04451176b163 – < d0b704e569ac3b8416d8e02270cdc9bf830ed395
  • Linux · Linux

    • affected 5.4
    • unaffected < 5.4
    • unaffected 5.10.265 – ≤ 5.10.*
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.151 – ≤ 6.6.*
    • unaffected 6.12.103 – ≤ 6.12.*
    • unaffected 6.18.44 – ≤ 6.18.*
    • unaffected 7.1.8 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-74549 badge
[![CVE-2026-74549](https://cveledger.app/badge/CVE-2026-74549.svg)](https://cveledger.app/cve/CVE-2026-74549)

Record last updated .