GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel Intel Speed Select: unvalidated ioctl indices reach MMIO offsets and NULL instances

UnscoredCVE-2026-89438Kernel, userspace & hypervisor+3 more CVEscurated

Impact

The Intel Speed Select Technology driver on Xeon hosts takes CPU ids, CLOS ids, socket ids and SST-PP level numbers straight from userspace ioctls and uses them to compute MMIO offsets or to index isst_common.sst_inst[]. Unvalidated values give out-of-bounds reads of the per-level offset table, an index one entry past the socket array, and dereference of a NULL instance pointer for a package with no bound TPMI instance - crashing the host or reading adjacent kernel memory. The practical exposure is a local user or container that holds the ISST character device; on a normal GPU node that device is root-owned, so this is a hardening fix rather than a tenant-reachable escape. A crash still costs a reboot of a node that cannot be drained cheaply. The kernel CNA split this across four ids (CVE-2026-89438, -89439, -89442, -89443); they are the same class of missing bounds and NULL checks in one driver with one remediation.

Who can reach it

Local user or privileged container able to open the ISST interface device on an Intel Xeon host. No remote path; no unauthenticated path.

What to do

Update to a stable kernel carrying all four fixes and reboot the affected hosts - drain the node first, since a GPU host cannot take a kernel reboot in place. No mitigation short of restricting access to the ISST device is described in the records. The records do not name specific fixed release numbers beyond the linked stable commits.

Also covers 3 CVEs

The vendor assigned a separate id to each affected code path. They share this advisory, this score and this fix, so they are one entry here.

CVE-2026-89439CVE-2026-89442CVE-2026-89443

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.