CVE-2024-34724
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 _UnrefAndMaybeDestroy of pmr.c, there is a possible arbitrary code execution due to a race condition. This could lead to local escalation of privilege in the kernel with no additional execution privileges needed. User interaction is not needed for exploitation.
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 race condition in the _UnrefAndMaybeDestroy function of pmr.c (kernel power management resource code) can be exploited to achieve arbitrary code execution in kernel context, enabling local privilege escalation without requiring additional user privileges or interaction.
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 dataall versionsCVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/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.
-
Check Android kernel versionRun 'uname -a' or check /proc/version to obtain the kernel version string. Also check Android OS version in Settings > About Phone > Android version.Affected if The kernel version predates the CVE-2024-34724 patch date (May 2024) and no security update has been applied.
-
Check Android security patch levelGo to Settings > About Phone > Security patch level or run 'getprop ro.build.version.security_patch' to retrieve the security patch date.Affected if The security patch level is earlier than the May 2024 Android security update containing the fix.
-
Verify pmr.c kernel module statusCheck if the power management resource (pmr) kernel code is present and active. On Android, examine /sys/kernel/debug/pmr/ if available, or check kernel config for CONFIG_PMR=y using 'cat /proc/config.gz' | gunzip | grep PMR.Affected if The pmr.c module is compiled into the kernel and actively managing power management resources.
-
Inspect _UnrefAndMaybeDestroy function presenceExamine the kernel symbols or debug info for the _UnrefAndMaybeDestroy function in the pmr subsystem. Use 'cat /proc/kallsyms' | grep -i pmr to check for pmr-related symbols.Affected if The _UnrefAndMaybeDestroy symbol exists in the running kernel, indicating the vulnerable code path is present.
A system is affected if it runs an Android kernel with the pmr.c power management resource code containing the vulnerable _UnrefAndMaybeDestroy function and has not received the May 2024 or later security patch for CVE-2024-34724.
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 the vendor-supplied kernel security patch for CVE-2024-34724 to all affected systems; given the kernel-level race condition, prioritize patching systems where untrusted local users could gain elevated privileges.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34724 — 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-34724 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