From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id CBCBD406822 for ; Sat, 15 Aug 2026 12:34:06 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786797247; cv=none; b=ifkCKaZMOGp/ZEr8sAkBZO1fMljT4uC77GGME+eDo/ynSFLKMyHILavMNFAhijC+xJfqVuGswT4rORXOU44qOH2ihXVDGrZTvZTBcUbuk61UVabnQnyvKfIuhmcdKb2R7P6br0oxDZWYhYZ5XV67VKGArGAS8uYnMxZAxqBU3xo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786797247; c=relaxed/simple; bh=WUiwCCVOvlev8+KbL7okSlxdEcrssz2V/d2f4WKHnaI=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=OUl3RizbZfwncj7b8BN+55BXDqGwChgpf6DXSeHAKZikSj2+cNlD07tlmy6t0IHJxdatxd7X8hplGwRESvhMgCENNeAT3PNLPHxHj6NrwJzlwB4llKJkh8OCS2yq8ypX89eeAGudBJgKigvLqoYv+sP42XsYi1mAv3yoLCpgcac= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=iYeaZ8sk; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="iYeaZ8sk" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2CCF51F000E9; Sat, 15 Aug 2026 12:34:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1786797246; bh=Fp+BXkesAKl83WhLIM9fQaiPen2lrL3zSxErecO/qWE=; h=From:To:Cc:Subject:Date:Reply-To; b=iYeaZ8sktxc6QHxZOA0Ypl65NacRA/05Pc8ZKyO+7wOS6WhrIUbQefzbKqgynBncq oH7Pr22lCu3amZAny7P2Dv/Rx8uF7xCKqrEoIcQijptc/7hcKitqrqsL4GFepsyd4o RVAPGBbY8vkimCk0Q0jDSwNkkGm+wS9C2zGJ1NBo= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-74551: hwmon: (nzxt-smart2) DMA-align output buffer Date: Sat, 15 Aug 2026 21:27:12 +0900 Message-ID: <2026081550-CVE-2026-74551-720e@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3317; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=W+1Rkuox2pdANqHrVcJDlpWYRebsKjASCfyBvj0Bi4c=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkNUeeeJaeJ84U/mPPI/bU5L/sjtxSx8O6MyMWejZVb2 8yV7+t0xLIwCDIxyIopsnzZxnN0f8UhRS9D29Mwc1iZQIYwcHEKwES0JzIsWPMnYQ93lQ6bp++0 O2nKpp2px1/8YJhfmrRMLVVU+zrfgufh25w7lu45+cAcAA== X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== 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. The Linux kernel CVE team has assigned CVE-2026-74551 to this issue. Affected and fixed versions =========================== Issue introduced in 5.17 with commit 53e68c20aeb1e23419bed811aa3a309ceda200f9 and fixed in 6.6.151 with commit 70ad543ce81f368411b6c721265a3b2d7ab4fda4 Issue introduced in 5.17 with commit 53e68c20aeb1e23419bed811aa3a309ceda200f9 and fixed in 6.12.103 with commit 51a76bc1b8e717ee3fc0d84f15ac51490ca5f76f Issue introduced in 5.17 with commit 53e68c20aeb1e23419bed811aa3a309ceda200f9 and fixed in 6.18.44 with commit 2332d35aaf206c17acf848522817252732596676 Issue introduced in 5.17 with commit 53e68c20aeb1e23419bed811aa3a309ceda200f9 and fixed in 7.1.8 with commit 6a2dbce5da2d2163a5b684acf68a0e54582ff0fa Issue introduced in 5.17 with commit 53e68c20aeb1e23419bed811aa3a309ceda200f9 and fixed in 7.2-rc6 with commit 080bbf42faf77e6489ab30d5114c5f8f6ccbb1b8 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-74551 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/hwmon/nzxt-smart2.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/70ad543ce81f368411b6c721265a3b2d7ab4fda4 https://git.kernel.org/stable/c/51a76bc1b8e717ee3fc0d84f15ac51490ca5f76f https://git.kernel.org/stable/c/2332d35aaf206c17acf848522817252732596676 https://git.kernel.org/stable/c/6a2dbce5da2d2163a5b684acf68a0e54582ff0fa https://git.kernel.org/stable/c/080bbf42faf77e6489ab30d5114c5f8f6ccbb1b8