hwmon: (nzxt-smart2) DMA-align output buffer
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 53e68c20aeb1e23419bed811aa3a309ceda200f9 · < 080bbf42faf77e6489ab30d5114c5f8f6ccbb1b8| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's nzxt-smart2 hwmon driver has an output buffer that is not DMA-aligned, which can corrupt adjacent variables on systems with non-coherent caches, such as ARM or MIPS. Operations that trigger an output report, such as setting a fan speed or updating the interval, cause the DMA mapping. The input does not describe an attacker, authentication requirement, or user-interaction requirement.
Check systems running the Linux kernel with the nzxt-smart2 hwmon driver, particularly on non-coherent CPU architectures; affected versions are not specified.