CVE-2025-67859
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA Improper Authentication vulnerability in TLP allows local users to arbitrarily control the power profile in use as well as the daemon’s log settings.This issue affects TLP: from 1.9 before 1.9.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceTLP versions 1.9 before 1.9.1 contain an improper authentication vulnerability allowing local users to bypass authentication controls and arbitrarily manipulate power profiles and the daemon's log settings. This is a local privilege escalation issue where the daemon does not properly validate user identity before accepting configuration changes.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify TLP is installedRun 'tlp --version' or check package manager: 'dpkg -l | grep tlp' (Debian) or 'rpm -q tlp' (RHEL)Affected if TLP is not installed, this CVE does not apply
-
Determine installed TLP versionExecute 'tlp --version' and note the output (e.g., 1.9.0, 1.9, 1.9.1, etc.)Affected if Version is 1.9 or 1.9.0 (any 1.9.x before 1.9.1)
-
Confirm TLP daemon is runningRun 'systemctl status tlp' or 'ps aux | grep tlp'Affected if Daemon is active and version is in the affected range (1.9.x before 1.9.1)
-
Check if any power profile configuration files existInspect /etc/tlp.d/ or ~/.config/tlp/ directories for configuration files that could be manipulatedAffected if Config files exist and TLP daemon is running an affected version
A user is affected if TLP version 1.9 or 1.9.0 is installed and the TLP daemon is running, allowing local users to bypass authentication and modify power profiles or log settings.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade TLP to version 1.9.1 or later to obtain the authentication fix. Verify that power management functionality operates normally after the upgrade.
TLP 1.9.1
- Check current TLP version with: tlp-stat -s or dpkg -l | grep tlp (Debian/Ubuntu) / rpm -qi tlp (RHEL/Fedora)
- Update your package repository: sudo zypper refresh (openSUSE/SUSE) or sudo apt update (Debian/Ubuntu)
- Upgrade TLP to version 1.9.1: sudo zypper in tlp=1.9.1 (openSUSE/SUSE) or sudo apt install tlp=1.9.1 (Debian/Ubuntu)
- If using a source-based install, download TLP 1.9.1 from https://github.com/linrunner/TLP/releases
- Restart the TLP service: sudo tlp start
- Verify the new version is installed: tlp-stat -s
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67859 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-67859 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data