dbcve.org
AndroidOperating system · Google

CVE-2024-32900

HIGH · 7.8 CVSS v3.1 Published 2024-06-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
In lwis_fence_signal of lwis_debug.c, there is a possible Use after Free due to improper locking. This could lead to local escalation of privilege from hal_camera_default SELinux label 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 confidence

Use-after-free vulnerability in the lwis_fence_signal function in lwis_debug.c caused by improper locking, allowing local privilege escalation from the hal_camera_default SELinux context without user interaction.

MitigationApply vendor patch for lwis driver to fix improper locking in lwis_fence_signal; may require kernel/receiver subsystem update.

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
AndroidOperating system
Affected:all versions

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device is running Google Android
    Check /system/build.prop for ro.build.fingerprint or ro.product.model to verify the device is Google Android
    Affected if Device is a Google Android device - all versions are affected per vendor advisory
  2. Identify if lwis driver is present
    Check /proc/config.gz or kernel config for CONFIG_LWIS or search /sys/module/ for 'lwis' module; also check /dev/ for lwis-related device nodes
    Affected if lwis driver component exists in the kernel - vulnerability resides in this driver
  3. Check kernel version and patch level
    Check /proc/version or 'uname -a' output; compare against Google's monthly security patch dates
    Affected if Kernel version predates the security patch containing the lwis fix for CVE-2024-32900
  4. Inspect lwis_debug.c for vulnerable function
    If kernel source is accessible, locate lwis_debug.c and search for lwis_fence_signal function; examine lock usage around fence signal operations
    Affected if Source contains lwis_fence_signal with improper locking patterns (unlock before use-after-free condition)
  5. Check for related crash logs
    Review dmesg or /sys/fs/pstore/ for uaf/crash logs mentioning lwis_fence or lwis driver failures
    Affected if Kernel crashes or memory errors related to lwis driver are present in logs

Environment is affected if it is a Google Android device with the lwis driver present and the kernel predates the CVE-2024-32900 security patch.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch for lwis driver to fix improper locking in lwis_fence_signal; may require kernel/receiver subsystem update.

Recommended fix Moderate confidence

Latest Android security patch level containing the fix for CVE-2024-32900 (refer to Android Security Bulletin)

  1. 1. Check the Android Security Bulletin for CVE-2024-32900 at source.android.com/security/bulletin to identify the specific security patch level containing the fix
  2. 2. Apply the latest Android security patch update available for your device from your device manufacturer
  3. 3. Verify the patch level by going to Settings > About Phone > Build Number and confirming it matches or exceeds the patched security patch level
Caveat Security updates typically have minimal breaking changes; however, ensure device compatibility before applying

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-32900 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-32900 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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