CVE-2026-74551

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: (nzxt-smart2) DMA-align output buffer

Sashiko reports:

When send_output_report() calls hid_hw_output_report(), the underlying USB HID core calls usb_interrupt_msg() which maps this buffer directly for DMA.

When the DMA mapping flushes or invalidates the cacheline, it will corrupt the adjacent variables (mutex, update_interval) that were modified concurrently by the CPU. This causes memory corruption due to cacheline sharing on non-coherent CPU architectures (such as ARM or MIPS). The DMA API debugging tool (CONFIG_DMA_API_DEBUG) will trigger runtime warnings for this violation.

Any operation that triggers send_output_report() (like setting a fan speed or updating the interval) causes the USB DMA mapping. On systems with non-coherent caches, this structural bug causes immediate and deterministic memory corruption.

Align the output buffer to ARCH_DMA_MINALIGN to fix the problem.

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: (nzxt-smart2) DMA-align output buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/70ad543ce81f368411b6c721265a3b2d7ab4fda4
generic

hwmon: (nzxt-smart2) DMA-align output buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6a2dbce5da2d2163a5b684acf68a0e54582ff0fa
generic

hwmon: (nzxt-smart2) DMA-align output buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/51a76bc1b8e717ee3fc0d84f15ac51490ca5f76f
generic

hwmon: (nzxt-smart2) DMA-align output buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2332d35aaf206c17acf848522817252732596676
generic

hwmon: (nzxt-smart2) DMA-align output buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/080bbf42faf77e6489ab30d5114c5f8f6ccbb1b8

Vendor Advisories for CVE-2026-74551(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 31× in last 7d / 31× 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-20 22:56 UTCEPSS rescore
  2. 2026-08-20 16:13 UTCGHSA enrichment
  3. 2026-08-20 04:56 UTCGHSA enrichment
  4. 2026-08-19 17:38 UTCEG score recompute
  5. 2026-08-19 17:38 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 16:52 UTCEG score recompute
  8. 2026-08-19 16:52 UTCGHSA enrichment
  9. 2026-08-19 15:35 UTCGHSA enrichment
  10. 2026-08-19 04:17 UTCGHSA enrichment
  11. 2026-08-18 16:59 UTCEG score recompute
  12. 2026-08-18 16:59 UTCGHSA enrichment
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 13:49 UTCEPSS rescore
  15. 2026-08-18 05:01 UTCGHSA enrichment
  16. 2026-08-17 17:43 UTCEG score recompute
  17. 2026-08-17 17:43 UTCGHSA enrichment
  18. 2026-08-17 13:47 UTCEPSS rescore
  19. 2026-08-17 06:23 UTCEG score recompute
  20. 2026-08-17 06:23 UTCGHSA enrichment
  21. 2026-08-17 05:54 UTCEG score recompute 7.80
  22. 2026-08-17 05:54 UTCGHSA enrichment
  23. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  24. 2026-08-17 05:39 UTCEG score recompute
  25. 2026-08-17 05:39 UTCGHSA enrichment
Show 6 more
  1. 2026-08-17 05:39 UTCMITRE cvelistV5
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-15 13:27 UTCNVD update
  5. 2026-08-15 12:38 UTCEG score recompute
  6. 2026-08-15 12:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74551?
CVE-2026-74551 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: hwmon: (nzxt-smart2) DMA-align output buffer Sashiko reports: When sendoutputreport() calls hidhwoutput_report(), the underlying USB HID core calls usbinterruptmsg() which maps this buffer directly for DMA. When the DMA mapping…
When was CVE-2026-74551 disclosed?
CVE-2026-74551 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-74551 actively exploited?
CVE-2026-74551 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 97.0% of all scored CVEs.
What is the CVSS score of CVE-2026-74551?
CVE-2026-74551 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-74551?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74551, 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-74551

Explore →

Is Your Infrastructure Affected by CVE-2026-74551?

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