CVE-2014-1419
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 · uneditedRace condition in the power policy functions in policy-funcs in acpi-support before 0.142 allows local users to gain privileges via unspecified vectors.
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 confidenceRace condition in the power policy functions in policy-funcs in acpi-support before version 0.142 allows local users to gain privileges. The vulnerability is a time-of-check to time-of-use (TOCTOU) issue in ACPI power management code where an attacker could exploit a timing window to escalate privileges to root.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 0.141= 12.04CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:M/Au:N/C:C/I:C/A:C
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.
-
Confirm acpi-support package is installedRun `dpkg -l acpi-support` or `dpkg -s acpi-support` to check if the package is present on the systemAffected if Package is not installed - the vulnerability does not apply
-
Check installed acpi-support versionRun `dpkg -l | grep acpi-support` or `apt-cache policy acpi-support` to obtain the exact version number installedAffected if Version is 0.141 or lower, indicating the vulnerable code is present
-
Verify Ubuntu 12.04 releaseRun `lsb_release -r` or check `/etc/lsb-release` to confirm the Ubuntu versionAffected if System is Ubuntu 12.04 and acpi-support version is 0.141 or lower - both conditions must match for full CVE applicability
-
Locate policy-funcs fileCheck for the presence of policy-funcs in paths such as `/usr/lib/pm-utils/policy-funcs` or search with `find /usr -name policy-funcs 2>/dev/null`Affected if The file exists in the expected location - indicates the vulnerable power policy code is in use
System is affected if it runs Ubuntu 12.04 with acpi-support version 0.141 or lower, where the policy-funcs file containing the TOCTOU race condition is present.
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.
From vendor dataUpgrade acpi-support to version 0.142 or later to patch the race condition vulnerability in the power policy functions.
- 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-2014-1419 — 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-2014-1419 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