CVE-2026-72396
CVE CVE-2026-72396EUVD EUVD-2026-59295Published 2026-08-15T05:56:23.000ZLast changed 2026-08-17T05:13:52.000Z
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 6.1.178; patch: 7.2; 87102808d03948c825c3bdc48316e48f6422fd7e <57d583f069fa9d3d0c0831e34b967d1f61edae94; patch: 0; patch: 5.15.212; 87102808d03948c825c3bdc48316e48f6422fd7e <82e4ab03a6ab9b87667410f5143bc484d7a62bdc; 87102808d03948c825c3bdc48316e48f6422fd7e <36554592e2f5cac16ff8bf73720d38a6d9ef4a20; patch: 6.12.97; patch: 6.18.40; 87102808d03948c825c3bdc48316e48f6422fd7e <c9e04a52663bc6651c06c2427df088b751062bd6; patch: 7.1.5; patch: 6.6.145; 87102808d03948c825c3bdc48316e48f6422fd7e <39a581bd64a0e91112ec8017a2dd4e70c1336e99; 87102808d03948c825c3bdc48316e48f6422fd7e <553f9517813912a5ab661af5504485d96824a61c; 87102808d03948c825c3bdc48316e48f6422fd7e <aa35cee30686e6be3c890bf741429c5025d55abe; 87102808d03948c825c3bdc48316e48f6422fd7e <93b96e723bdcba6172a5814262be875abcc5d269; patch: 5.10.261; 3.3
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.