Skip to content
Noroxi
CVE-2026-80663· NVD / CVE Program· CNA Linux

tools/power/x86/intel-speed-select: Harden daemon pidfile open

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.

HighCVSS 7.1 · v3.1—No exploit Fix available

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help
Published
Aug 28, 2026
Updated
Aug 29, 2026
EPSS
0.2% · 6th percentile
CWE
—
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CNA vs NVD score

NVD
—
CNA · Linux
7.1
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.18affected
    • 7fd786dfbd2c55ddee3b87f33c82f1c58bdb1dd6 and later · before 905493a6338c82a70da16f86e0a6215db5a3d73daffected · git
    • 7fd786dfbd2c55ddee3b87f33c82f1c58bdb1dd6 and later · before db938eb9a3c1317596c28e94413b33426508d51baffected · git
    • 7fd786dfbd2c55ddee3b87f33c82f1c58bdb1dd6 and later · before 72a07abc6b9046f07a08bba353cad7667bcc9dceaffected · git
    • 7fd786dfbd2c55ddee3b87f33c82f1c58bdb1dd6 and later · before 19ffeb30fdfce63f8d6aca71bcdddb3f69d46278affected · git
    • 7fd786dfbd2c55ddee3b87f33c82f1c58bdb1dd6 and later · before e8adac69d1bdf035ef97cc914e845acd4ef08e28affected · git
    • 7fd786dfbd2c55ddee3b87f33c82f1c58bdb1dd6 and later · before 607af438e6430893a822964c841a1994b33accccaffected · git
    • before 5.18not affected · semver
    • 6.1.178 and later · up to and including 6.1.*not affected · semver
    • 6.6.145 and later · up to and including 6.6.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.5-17.1.5-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan
  • CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler
    40Plan
  • CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index
    40Plan
  • CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux19ffeb30fdfce63f8d6aca71bcdddb3f69d46278Vendor (CNA)
Linux Linux607af438e6430893a822964c841a1994b33accccVendor (CNA)
Linux Linux72a07abc6b9046f07a08bba353cad7667bcc9dceVendor (CNA)
Linux Linux905493a6338c82a70da16f86e0a6215db5a3d73dVendor (CNA)
Linux Linuxdb938eb9a3c1317596c28e94413b33426508d51bVendor (CNA)
Linux Linuxe8adac69d1bdf035ef97cc914e845acd4ef08e28Vendor (CNA)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records