CVE-2026-74551: hwmon: (nzxt-smart2) DMA-align output buffer
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 080bbf42faf77e6489ab30d5114c5f8f6ccbb1b8, 2332d35aaf206c17acf848522817252732596676, 51a76bc1b8e717ee3fc0d84f15ac51490ca5f76f.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 080bbf42faf77e6489ab30d5114c5f8f6ccbb1b8, 2332d35aaf206c17acf848522817252732596676, 51a76bc1b8e717ee3fc0d84f15ac51490ca5f76f or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 15, 2026
- Updated
- Aug 19, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.17affected
- 53e68c20aeb1e23419bed811aa3a309ceda200f9 and later · before 81a6593b1c8dfb2694cd0ce39be01212d2b8436caffected · git
- 53e68c20aeb1e23419bed811aa3a309ceda200f9 and later · before 70ad543ce81f368411b6c721265a3b2d7ab4fda4affected · git
- 53e68c20aeb1e23419bed811aa3a309ceda200f9 and later · before 51a76bc1b8e717ee3fc0d84f15ac51490ca5f76faffected · git
- 53e68c20aeb1e23419bed811aa3a309ceda200f9 and later · before 2332d35aaf206c17acf848522817252732596676affected · git
- 53e68c20aeb1e23419bed811aa3a309ceda200f9 and later · before 6a2dbce5da2d2163a5b684acf68a0e54582ff0faaffected · git
- 53e68c20aeb1e23419bed811aa3a309ceda200f9 and later · before 080bbf42faf77e6489ab30d5114c5f8f6ccbb1b8affected · git
- before 5.17not affected · semver
- 6.1.183 and later · up to and including 6.1.*not affected · semver
- 6.6.151 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.8-1 | 7.1.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74545Aug 15, 2026 · rtase: fix double free of multi-frag skb on DMA map failure39Monitor
- ← EarlierCVE-2026-74549Aug 15, 2026 · hwmon: (nct6775-core) Prevent access to unsupported weight registers31Monitor
- Later →CVE-2026-74552Aug 15, 2026 · hwmon: (lm90) Only report alarms if driver is ready0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 080bbf42faf77e6489ab30d5114c5f8f6ccbb1b8 | Vendor (CNA) |
| Linux Linux | 2332d35aaf206c17acf848522817252732596676 | Vendor (CNA) |
| Linux Linux | 51a76bc1b8e717ee3fc0d84f15ac51490ca5f76f | Vendor (CNA) |
| Linux Linux | 6a2dbce5da2d2163a5b684acf68a0e54582ff0fa | Vendor (CNA) |
| Linux Linux | 70ad543ce81f368411b6c721265a3b2d7ab4fda4 | Vendor (CNA) |
| Linux Linux | 81a6593b1c8dfb2694cd0ce39be01212d2b8436c | Vendor (CNA) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0854 · Aug 19, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/2332d35aaf206c17acf848522817252732596676
- git.kernel.org/stable/c/51a76bc1b8e717ee3fc0d84f15ac51490ca5f76f
- git.kernel.org/stable/c/6a2dbce5da2d2163a5b684acf68a0e54582ff0fa
- git.kernel.org/stable/c/70ad543ce81f368411b6c721265a3b2d7ab4fda4
- git.kernel.org/stable/c/81a6593b1c8dfb2694cd0ce39be01212d2b8436c
Vendor advisories and official records. Exploit/PoC links are deliberately left out.