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.
Published: 2026-08-28
Score: n/a
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability allows a local, unprivileged user to interfere with a root‑run daemon by creating a symlink at the daemon’s fixed pidfile location. The daemon fails to use the O_NOFOLLOW flag and does not validate the opened file with fstat() before writing, so it writes into whatever file the symlink points to. An attacker can therefore cause the daemon to write to an arbitrary root‑owned file of their choice, an operation that would normally be disallowed at the user level. This provides the attacker direct write privileges to root files and can lead to configuration tampering or compromise of system integrity.

Affected Systems

All Linux kernel builds that contain the older implementation of the intel-speed-select daemon are affected. No specific vendor or kernel version is listed, so all distributions using the affected kernel before the patch are impacted.

Risk and Exploitability

The attack requires no special privileges beyond the ability to create a symlink in the daemon’s pidfile directory, which is typically /tmp and writable by all users. Because the daemon runs as root, the local user gains the ability to modify any file the daemon can access, which is a significant escalation. The EPSS score is unavailable, and the vulnerability is not listed in CISA’s KEV catalog. The practical risk is high for systems where the daemon is running as root and the pidfile directory is world‑writable.

Generated by OpenCVE AI on August 28, 2026 at 11:53 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a version that includes the fix for the pidfile O_NOFOLLOW issue.
  • If upgrading is not immediately possible, modify the pidfile location to a directory owned by root and not world‑writable, such as /var/run, to prevent unprivileged users from creating symlinks there.
  • As a temporary measure, configure the daemon or the kernel to open the pidfile with the O_NOFOLLOW flag and validate the file with fstat() before writing, eliminating the symlink race condition.

Generated by OpenCVE AI on August 28, 2026 at 11:53 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 28 Aug 2026 11:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-284
CWE-362

Fri, 28 Aug 2026 07:30:00 +0000

Type Values Removed Values Added
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.
Title tools/power/x86/intel-speed-select: Harden daemon pidfile open
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-28T06:49:06.882Z

Reserved: 2026-08-26T14:34:25.781Z

Link: CVE-2026-80663

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-28T08:16:51.503

Modified: 2026-08-28T08:16:51.503

Link: CVE-2026-80663

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-28T12:00:10Z

Weaknesses
  • CWE-284

    Improper Access Control

  • CWE-362

    Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')