CVE-2026-72396

hwmon: adm1275: Prevent reading uninitialized stack

N/A
Published: August 15, 2026 at 05:56 AM UTC
Updated: August 17, 2026 at 06:19 AM 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: adm1275: Prevent reading uninitialized stack While adding support for the ROHM BD127X0 hot-swap controllers, sashiko reported an error in device-name comparison, which can lead to reading uninitialized stack memory. Quoting Sashiko: This is a pre-existing issue, but I noticed that just before this block in adm1275_probe(), there might be an out-of-bounds stack read: ret = i2c_smbus_read_block_data(client, PMBUS_MFR_MODEL, block_buffer); if (ret < 0) { ... } for (mid = adm1275_id; mid->name[0]; mid++) { if (!strncasecmp(mid->name, block_buffer, strlen(mid->name))) break; } Since i2c_smbus_read_block_data() reads up to 32 bytes into the uninitialized stack array block_buffer without appending a null terminator, strncasecmp() could read past the valid bytes returned in ret. For example, if the device returns a shorter string like "adm12", checking it against "adm1275" up to the length of "adm1275" will continue reading into uninitialized stack bounds. Prevent reading uninitialized memory by zeroing the stack array.

Affected

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

3.3 ≤ v < 5.10.2613.3 ≤ v < 5.15.2123.3 ≤ v < 6.1.1783.3 ≤ v < 6.12.973.3 ≤ v < 6.18.403.3 ≤ v < 6.6.1453.3 ≤ v < 7.1.53.3 ≤ v < 7.23.387102808d03948c825c3bdc48316e48f6422fd7e
Vendor states this is fixed in 36554592e2f5cac16ff8bf73720d38a6d9ef4a20 (fixed)
Vendor states this is fixed in 39a581bd64a0e91112ec8017a2dd4e70c1336e99 (fixed)
Vendor states this is fixed in 553f9517813912a5ab661af5504485d96824a61c (fixed)
Vendor states this is fixed in 57d583f069fa9d3d0c0831e34b967d1f61edae94 (fixed)
Vendor states this is fixed in 82e4ab03a6ab9b87667410f5143bc484d7a62bdc (fixed)
Vendor states this is fixed in 93b96e723bdcba6172a5814262be875abcc5d269 (fixed)
Vendor states this is fixed in aa35cee30686e6be3c890bf741429c5025d55abe (fixed)
Vendor states this is fixed in c9e04a52663bc6651c06c2427df088b751062bd6 (fixed)
Vendor states this is fixed in 3.3 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (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