From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80663: tools/power/x86/intel-speed-select: Harden daemon pidfile open
Date: Fri, 28 Aug 2026 08:49:40 +0200 [thread overview]
Message-ID: <2026082846-CVE-2026-80663-bdef@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
tools/power/x86/intel-speed-select: Harden daemon pidfile open
Avoid symlink-based pidfile clobbering by opening the pidfile with
O_NOFOLLOW and validating it with fstat() before locking/writing.
The daemon currently uses a fixed pidfile path under /tmp. A local
unprivileged user can pre-create a symlink at that path and cause a
root-run daemon instance to write into an attacker-chosen file.
The Linux kernel CVE team has assigned CVE-2026-80663 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.18 with commit 7fd786dfbd2c55ddee3b87f33c82f1c58bdb1dd6 and fixed in 6.1.178 with commit 905493a6338c82a70da16f86e0a6215db5a3d73d
Issue introduced in 5.18 with commit 7fd786dfbd2c55ddee3b87f33c82f1c58bdb1dd6 and fixed in 6.6.145 with commit db938eb9a3c1317596c28e94413b33426508d51b
Issue introduced in 5.18 with commit 7fd786dfbd2c55ddee3b87f33c82f1c58bdb1dd6 and fixed in 6.12.97 with commit 72a07abc6b9046f07a08bba353cad7667bcc9dce
Issue introduced in 5.18 with commit 7fd786dfbd2c55ddee3b87f33c82f1c58bdb1dd6 and fixed in 6.18.40 with commit 19ffeb30fdfce63f8d6aca71bcdddb3f69d46278
Issue introduced in 5.18 with commit 7fd786dfbd2c55ddee3b87f33c82f1c58bdb1dd6 and fixed in 7.1.5 with commit e8adac69d1bdf035ef97cc914e845acd4ef08e28
Issue introduced in 5.18 with commit 7fd786dfbd2c55ddee3b87f33c82f1c58bdb1dd6 and fixed in 7.2 with commit 607af438e6430893a822964c841a1994b33acccc
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-80663
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:
tools/power/x86/intel-speed-select/isst-daemon.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/905493a6338c82a70da16f86e0a6215db5a3d73d
https://git.kernel.org/stable/c/db938eb9a3c1317596c28e94413b33426508d51b
https://git.kernel.org/stable/c/72a07abc6b9046f07a08bba353cad7667bcc9dce
https://git.kernel.org/stable/c/19ffeb30fdfce63f8d6aca71bcdddb3f69d46278
https://git.kernel.org/stable/c/e8adac69d1bdf035ef97cc914e845acd4ef08e28
https://git.kernel.org/stable/c/607af438e6430893a822964c841a1994b33acccc
reply other threads:[~2026-08-28 6:52 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=2026082846-CVE-2026-80663-bdef@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.