CVE-2026-74553

hwmon: (nct6775-core) Fix number of temperature registers for NCT6116

N/A
Published: August 15, 2026 at 12:27 PM UTC
Updated: August 19, 2026 at 05:21 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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 nct6775_probe+0x936/0x46f0 [nct6775] Read of size 2 at addr ffffffffc19561a6 by task modprobe/954 ... Call Trace: dump_stack+0x7d/0xa7 print_address_description.constprop.0+0x1c/0x220 ? __kasan_kmalloc.constprop.0+0xc9/0xd0 ? __kmalloc_node_track_caller+0x194/0x5b0 ? nct6775_probe+0x936/0x46f0 [nct6775] ? nct6775_probe+0x936/0x46f0 [nct6775] ... Fix the problem by hard-coding the number of temperature and temperature configuration registers to three for NCT6116. Drop the unnecessary NCT6116_REG_TEMP_SOURCE array and re-use NCT6106_REG_TEMP_SOURCE.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.4 ≤ v < 6.1.1835.4 ≤ v < 6.12.1035.4 ≤ v < 6.18.445.4 ≤ v < 6.6.1515.4 ≤ v < 7.1.85.4 ≤ v < 7.229c7cb485b321c024dedc168bcbb04451176b1635.4
Vendor states this is fixed in 16c45bb3d3434cfb9ea264fa52090d0823240465 (fixed)
Vendor states this is fixed in 739d7fc6b6f662c8286912157f0c4912388aa292 (fixed)
Vendor states this is fixed in 9a87dfaa05c3c9d3a4cdb7eafc1ab4abc84f6eef (fixed)
Vendor states this is fixed in a42d727dae5701deac8bb2a75effadae7d681153 (fixed)
Vendor states this is fixed in a7f47f5246cd6c3199e5fb2d4109cc53e766e3f0 (fixed)
Vendor states this is fixed in b0e8adb2ccb43009796897ced09f91636685c9d3 (fixed)
Vendor states this is fixed in 5.4 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.103 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 6.6.151 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card