Look up another CVE · open CVE-2026-89442 in the interactive tracker
CVE-2026-89442
platform/x86: ISST: Validate socket ID in clos_assoc ioctl
Published 2026-09-11 (37 days ago) by the Linux kernel CNA. Subsystem drivers/platform. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-89442 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | fixedDSA-6528-1 · 2026-09-29 · text | 6.12.111-1 | Update the kernel and reboot. DSA-6528-1 shipped the fix on 2026-09-29, in 6.12.111-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian 12bookworm · linux-6.12 | fixedDLA-4817-1 · 2026-10-04 · text | 6.12.111-1~deb12u1 | Update the kernel and reboot. DLA-4817-1 shipped the fix on 2026-10-04, in 6.12.111-1~deb12u1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
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().
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/platform/x86/intel/speed_select_if/isst_tpmi_core.c
- What this is
- INTEL SPEED SELECT TECHNOLOGYMAINTAINERS section matched on drivers/platform/x86/intel/speed_select_if/ · platform-driver-x86@vger.kernel.org · Maintained
- Kernel module
- isst_tpmi_core
Check it on the machine
grep -wE 'CONFIG_INTEL_SPEED_SELECT_INTERFACE|CONFIG_INTEL_SPEED_SELECT_TPMI|CONFIG_X86' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w isst_tpmi_corePrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed. The build rule could not be established for 1 release, so nothing is claimed about those.
- bookworm?
- trixieMnot built on amd64/cloud-amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt/arm64, armel/rpi, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- forky, sidMnot built on amd64/cloud-amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt-arm64, armhf/armmp, armhf/armmp-lpae, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- bookworm · linux-6.12Mnot built on amd64/cloud-amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt/arm64, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le, ppc64el/powerpc64le-64k
- ?
- not established - no Makefile entry for the affected file
- M
- a module where it is built at all; some flavours do not build it
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
- Build switches
- CONFIG_INTEL_SPEED_SELECT_INTERFACE, CONFIG_INTEL_SPEED_SELECT_TPMI, CONFIG_X86
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-09-11 (37 days ago)source
- CVSS
- 7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.17%, higher than 5.7% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- drivers/platform
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.4 | 6.6.157 | c847ea4851ec |
| 6.4 | 6.12.109 | 0d90ab5f80e1 |
| 6.4 | 6.18.50 | 82e707eff9e3 |
| 6.4 | 7.2.4 | 207b4dc6eb10 |
| 6.4 | 7.3 | a89f07db0cb9 |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4817-1 | 2026-10-04 | bookworm 6.12.111-1~deb12u1 | tracker |
| DSA-6528-1 | 2026-09-29 | trixie 6.12.111-1 | tracker |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- The bug is reached only through the ISST_IF_CLOS_ASSOC ioctl on /dev/isst_interface; isst_if_clos_assoc() is not invoked from network, Bluetooth, or USB processing.
- AC:LAttack complexity, low
- The attacker sets punit_cpu_map=1 and socket_id equal to topology_max_packages() (one past sst_inst[]) or to an in-range unbound package (NULL sst_inst). Both are deterministic ioctl inputs with no race or victim state.
- PR:LPrivileges required, low
- isst_if_open() has no capability check, and capable(CAP_SYS_ADMIN) runs only on the SET path after sst_inst is already indexed and dereferenced, so an unprivileged local user with the device fd can trigger it via GET.
- UI:NUser interaction, none
- The attacker issues the ioctl directly against /dev/isst_interface; no victim action such as mounting a filesystem or opening a file is required.
- S:UScope, unchanged
- The out-of-bounds pointer load and subsequent NULL or wild dereference stay in the kernel ISST driver and do not cross a VM, IOMMU, or sandbox boundary.
- C:HConfidentiality impact, high
- socket_id == topology_max_packages() reads one pointer past sst_inst[] and treats it as struct tpmi_sst_struct; map_partition_power_domain_id() and readq() follow that object, and GET copy_to_user discloses the result as a kernel-memory read primitive.
- I:HIntegrity impact, high
- Treating the adjacent out-of-bounds pointer as sst_inst is type confusion; the confused object supplies sst_base used for writeq() on the SET path and further structure walks, which is an exploitable kernel write primitive.
- A:HAvailability impact, high
- A NULL sst_inst or garbage out-of-bounds pointer is immediately dereferenced in map_partition_power_domain_id() and the following power_domain_info access, causing a kernel oops or panic.