CVE-2026-89442
CVE CVE-2026-89442EUVD EUVD-2026-76348Published 2026-09-11T19:43:10.000ZLast changed 2026-09-14T11:59:52.000ZCVSS 7.8
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: platform/x86: ISST: Validate socket ID in clos_assoc ioctl isst_if_clos_assoc() validates the user-supplied socket_id with 'socket_id > topology_max_packages()', but isst_common.sst_inst[] is allocated with topology_max_packages() entries, so the valid index range is [0, topology_max_packages()). The '>' comparison lets socket_id == topology_max_packages() pass and index one entry past the array. In addition, isst_common.sst_inst[socket_id] is NULL for an in-range package that has no bound TPMI SST instance, and the pointer is used without a NULL check. Both the out-of-bounds entry and the NULL pointer are then dereferenced by map_partition_power_domain_id() and the following power_domain_info access. Reject socket_id >= topology_max_packages() and a NULL sst_inst, matching the checks already performed by get_instance().
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.12.109; 12a7d2cb811dd8a884dea088a2701fcb8d00136e <207b4dc6eb100141b122b2602504a1429a4b6558; patch: 6.6.157; patch: 7.3-rc1; patch: 6.18.50; 12a7d2cb811dd8a884dea088a2701fcb8d00136e <c847ea4851ecfa3462cc711ded2c3c3dd8d08ab8; 6.4; 12a7d2cb811dd8a884dea088a2701fcb8d00136e <0d90ab5f80e19cddfeb0c9fab47a1f34aa932075; patch: 0; 12a7d2cb811dd8a884dea088a2701fcb8d00136e <82e707eff9e3b7ef6d96ecc23ea8876d20c7d6ca; patch: 7.2.4; 12a7d2cb811dd8a884dea088a2701fcb8d00136e <a89f07db0cb95c54dac4a8406c79a04e44a73c3c
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.