CVE-2024-20140
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 · uneditedIn power, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: ALPS09270402; Issue ID: MSV-2020.
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 confidenceA missing bounds check in the power management subsystem allows an out-of-bounds write, enabling local privilege escalation for an attacker who already has System-level access. The vulnerability requires no user interaction and stems from inadequate input validation in power-related code.
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= 3.3= 4.0= 5.0= 12.0= 13.0= 14.0= 15.0CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify your operating system platformDetermine if your system runs Linuxfoundation Yocto or Google Android. For Android, check Settings > About Phone > Android version. For Yocto, check /etc/os-release or the yocto-release file.Affected if The platform is Linuxfoundation Yocto versions 3.3, 4.0, or 5.0, OR Google Android versions 12.0, 13.0, 14.0, or 15.0
-
Confirm the exact version numberCompare your installed version against the affected ranges. On Android: settings or 'getprop ro.build.version.release'. On Yocto: 'cat /etc/os-release' or check the deployed image version.Affected if The version exactly matches 3.3, 4.0, or 5.0 for Yocto, or 12.0, 13.0, 14.0, or 15.0 for Android
-
Verify power management subsystem is activeCheck if the power management subsystem is enabled and running. On Android, examine running services related to power (ps -A | grep power) or check /sys/power/ state. On Yocto, check kernel config for power management options or review active power management daemons.Affected if The power management subsystem is actively running on an affected version
-
Audit System-level accessSince exploitation requires System privilege, review accounts with System or root access. List privileged users (who, id, groups on Android; getent passwd or sudo -l on Yocto) and check for unauthorized or unexpected accounts.Affected if Multiple accounts have System/root access or unauthorized privileged accounts exist on an affected version
You are affected if your system runs Linuxfoundation Yocto 3.3, 4.0, or 5.0 OR Google Android 12.0, 13.0, 14.0, or 15.0, with the power management subsystem active and multiple privileged accounts 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 dataApply patch ALPS09270402 immediately. Since exploitation requires System privilege, audit privileged account access and monitor for suspicious power subsystem interactions as a defense-in-depth measure.
- Consultation3.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,896.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20140 — 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-2024-20140 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