From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72143: platform/x86: ISST: Restore SST-PP control to all domains
Date: Sat, 15 Aug 2026 15:03:42 +0900 [thread overview]
Message-ID: <2026081532-CVE-2026-72143-fed4@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
platform/x86: ISST: Restore SST-PP control to all domains
The SST-PP control offset is only restored to power domain 0 after
resume. During suspend, control values are read and stored for all
power domains.
Use pd_info->sst_base instead of power_domain_info->sst_base, which
only points to power domain 0 base address.
The Linux kernel CVE team has assigned CVE-2026-72143 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.18.16 with commit e3704ce5d7156ee837461be99841f312c64700b0 and fixed in 6.18.40 with commit cea03d67db3a880893360bdbb1b0b8d9b33b1799
Issue introduced in 7.0 with commit dc7901b5a1563a9c9eb29b3b0b0dac3162065cd8 and fixed in 7.1.5 with commit 2a42f651cce91e9cbe65fe933622c522cbb1868b
Issue introduced in 7.0 with commit dc7901b5a1563a9c9eb29b3b0b0dac3162065cd8 and fixed in 7.2-rc1 with commit 2565a28cdcdcb035e151d285efcba26bccb3726e
Issue introduced in 6.19.6 with commit 2624f3bf45a830cb3b8c8b967b23a72139700562
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-72143
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/platform/x86/intel/speed_select_if/isst_tpmi_core.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/cea03d67db3a880893360bdbb1b0b8d9b33b1799
https://git.kernel.org/stable/c/2a42f651cce91e9cbe65fe933622c522cbb1868b
https://git.kernel.org/stable/c/2565a28cdcdcb035e151d285efcba26bccb3726e
reply other threads:[~2026-08-15 6:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026081532-CVE-2026-72143-fed4@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.