CVE-2026-74549

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-15. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 19, 2026

Advisory Details (5)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

hwmon: (nct6775-core) Prevent access to unsupported weight registers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d0b704e569ac3b8416d8e02270cdc9bf830ed395
generic

hwmon: (nct6775-core) Prevent access to unsupported weight registers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/689082a4cb166a7ae9729f7b12339e69fdad6c52
generic

hwmon: (nct6775-core) Prevent access to unsupported weight registers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4ad2972ef0e1bd1018ad7a72661a4636ed7daecc
generic

hwmon: (nct6775-core) Prevent access to unsupported weight registers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/25b528816f5d83be5236dc182692369e8c9402b0
generic

hwmon: (nct6775-core) Prevent access to unsupported weight registers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1b722740ac5c2b2070f9ba922f4e0f227faf0246

Vendor Advisories for CVE-2026-74549(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 32× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 04:21 UTCEG score recompute
  2. 2026-08-21 04:21 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 16:47 UTCGHSA enrichment
  5. 2026-08-20 05:13 UTCGHSA enrichment
  6. 2026-08-19 17:38 UTCEG score recompute
  7. 2026-08-19 17:38 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 16:53 UTCEG score recompute
  10. 2026-08-19 16:52 UTCGHSA enrichment
  11. 2026-08-19 05:35 UTCGHSA enrichment
  12. 2026-08-18 18:03 UTCEG score recompute
  13. 2026-08-18 18:03 UTCGHSA enrichment
  14. 2026-08-18 13:49 UTCEPSS rescore
  15. 2026-08-18 13:49 UTCEPSS rescore
  16. 2026-08-18 06:27 UTCGHSA enrichment
  17. 2026-08-17 18:54 UTCEG score recompute
  18. 2026-08-17 18:54 UTCGHSA enrichment
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-17 06:23 UTCEG score recompute
  21. 2026-08-17 06:23 UTCGHSA enrichment
  22. 2026-08-17 05:54 UTCEG score recompute 7.80
  23. 2026-08-17 05:54 UTCGHSA enrichment
  24. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  25. 2026-08-17 05:39 UTCEG score recompute
Show 7 more
  1. 2026-08-17 05:39 UTCGHSA enrichment
  2. 2026-08-17 05:39 UTCMITRE cvelistV5
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-15 13:27 UTCNVD update
  6. 2026-08-15 12:38 UTCEG score recompute
  7. 2026-08-15 12:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74549?
CVE-2026-74549 is a high vulnerability published on August 15, 2026. 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…
When was CVE-2026-74549 disclosed?
CVE-2026-74549 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74549 actively exploited?
CVE-2026-74549 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.9% of all scored CVEs.
What is the CVSS score of CVE-2026-74549?
CVE-2026-74549 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-74549?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74549, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-74549

Explore →

Is Your Infrastructure Affected by CVE-2026-74549?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.