CVE-2026-74553: hwmon: (nct6775-core) Fix number of temperature registers for NCT6116
In the Linux kernel, the following vulnerability has been resolved:
hwmon: (nct6775-core) Fix number of temperature registers for NCT6116
Unlike NCT6106, NCT6116 only has three temperature registers, and with it only three temperature source and temperature source configuration registers. The register addresses match those of NCT6106 and can be re-used.
The code used a separate array to list the temperature source registers for NCT6116, but used the size of the NCT6106 register array to set the number of registers. The NCT6106 register array provides six addresses, while the temperature source register array for NCT6116 only provides three addresses. This causes a KASAN report.
BUG: KASAN: global-out-of-bounds in nct6775probe+0x936/0x46f0 [nct6775] Read of size 2 at addr ffffffffc19561a6 by task modprobe/954 ... Call Trace: dumpstack+0x7d/0xa7 printaddressdescription.constprop.0+0x1c/0x220 ? kasankmalloc.constprop.0+0xc9/0xd0 ? kmallocnodetrackcaller+0x194/0x5b0 ? nct6775probe+0x936/0x46f0 [nct6775] ? nct6775probe+0x936/0x46f0 [nct6775] ...
Fix the problem by hard-coding the number of temperature and temperature configuration registers to three for NCT6116. Drop the unnecessary NCT6116REGTEMPSOURCE array and re-use NCT6106REGTEMPSOURCE.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-74553?
CVE-2026-74553 has been assigned a risk score of 11, indicating a critical severity level.
What systems are affected by CVE-2026-74553?
CVE-2026-74553 affects Linux kernel implementations utilizing the NCT6116 hardware monitoring device.
How do I fix CVE-2026-74553?
To fix CVE-2026-74553, update to the patched version of the Linux kernel that addresses the vulnerability.
What impact does CVE-2026-74553 have on system security?
CVE-2026-74553 could potentially lead to inaccurate temperature readings, disrupting system monitoring and stability.
Is there a workaround for CVE-2026-74553 if I cannot update immediately?
There are no specific workarounds for CVE-2026-74553; updating the kernel is recommended for resolving the issue.