Bug 2532359 (CVE-2026-89442) - CVE-2026-89442 kernel: platform/x86: ISST: Validate socket ID in clos_assoc ioctl
Summary: CVE-2026-89442 kernel: platform/x86: ISST: Validate socket ID in clos_assoc i...
Keywords:
Status: NEW
Alias: CVE-2026-89442
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-11 22:32 UTC by OSIDB Bzimport
Modified: 2026-09-14 21:41 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-11 22:32:02 UTC
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().


Note You need to log in before you can comment on or make changes to this bug.