In the Linux kernel, the following vulnerability has been resolved: platform/x86: ISST: Validate socket ID in clos_assoc ioctl isst_if_clos_assoc()… (CVE-2026-89442)
A vulnerability in the Linux kernel's platform/x86 ISST component was resolved. The issue involves improper validation of the socket_id parameter in the clos_assoc ioctl call, allowing an out-of-bounds array access and potential NULL pointer dereference. The validation incorrectly permits socket_id equal to topology_max_packages(), which is outside the valid index range. Additionally, the code does not check for NULL pointers in certain cases, leading to unsafe dereferences. The fix rejects socket_id values greater than or equal to topology_max_packages() and NULL pointers, aligning with existing validation logic.
AI Analysis
Technical Summary
The Linux kernel's ISST (Intel Speed Select Technology) platform/x86 code had a vulnerability in the isst_if_clos_assoc() function where the socket_id parameter was validated with a '>' comparison against topology_max_packages(), allowing socket_id == topology_max_packages() to pass. This caused an out-of-bounds access on the isst_common.sst_inst[] array, which is allocated with topology_max_packages() entries indexed from 0 to topology_max_packages() - 1. Furthermore, the code dereferenced isst_common.sst_inst[socket_id] without checking for NULL, which could occur for valid socket IDs without a bound TPMI SST instance. These issues led to potential out-of-bounds and NULL pointer dereferences in map_partition_power_domain_id() and subsequent power_domain_info accesses. The vulnerability was fixed by rejecting socket_id values greater than or equal to topology_max_packages() and NULL sst_inst pointers, consistent with checks in get_instance().
Potential Impact
The vulnerability could lead to out-of-bounds memory access and NULL pointer dereference in the Linux kernel's ISST component. This may cause kernel crashes or undefined behavior. No information about active exploitation or broader impact is provided.
Mitigation Recommendations
A fix is available that properly validates the socket_id parameter by rejecting values greater than or equal to topology_max_packages() and checking for NULL pointers before dereferencing. Users should apply the official kernel update that includes this patch. No additional mitigation steps are indicated.
In the Linux kernel, the following vulnerability has been resolved: platform/x86: ISST: Validate socket ID in clos_assoc ioctl isst_if_clos_assoc()… (CVE-2026-89442)
Description
A vulnerability in the Linux kernel's platform/x86 ISST component was resolved. The issue involves improper validation of the socket_id parameter in the clos_assoc ioctl call, allowing an out-of-bounds array access and potential NULL pointer dereference. The validation incorrectly permits socket_id equal to topology_max_packages(), which is outside the valid index range. Additionally, the code does not check for NULL pointers in certain cases, leading to unsafe dereferences. The fix rejects socket_id values greater than or equal to topology_max_packages() and NULL pointers, aligning with existing validation logic.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's ISST (Intel Speed Select Technology) platform/x86 code had a vulnerability in the isst_if_clos_assoc() function where the socket_id parameter was validated with a '>' comparison against topology_max_packages(), allowing socket_id == topology_max_packages() to pass. This caused an out-of-bounds access on the isst_common.sst_inst[] array, which is allocated with topology_max_packages() entries indexed from 0 to topology_max_packages() - 1. Furthermore, the code dereferenced isst_common.sst_inst[socket_id] without checking for NULL, which could occur for valid socket IDs without a bound TPMI SST instance. These issues led to potential out-of-bounds and NULL pointer dereferences in map_partition_power_domain_id() and subsequent power_domain_info accesses. The vulnerability was fixed by rejecting socket_id values greater than or equal to topology_max_packages() and NULL sst_inst pointers, consistent with checks in get_instance().
Potential Impact
The vulnerability could lead to out-of-bounds memory access and NULL pointer dereference in the Linux kernel's ISST component. This may cause kernel crashes or undefined behavior. No information about active exploitation or broader impact is provided.
Mitigation Recommendations
A fix is available that properly validates the socket_id parameter by rejecting values greater than or equal to topology_max_packages() and checking for NULL pointers before dereferencing. Users should apply the official kernel update that includes this patch. No additional mitigation steps are indicated.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-66vv-5f3v-p2fx
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-89442"]
Threat ID: 6aa4a02755bf5e2cf5a86b04
Added to database: 09/12/2026, 00:43:19 UTC
Last enriched: 09/12/2026, 01:19:08 UTC
Last updated: 09/12/2026, 01:19:08 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.