CVE-2024-29787
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 lwis_process_transactions_in_queue of lwis_transaction.c, there is a possible use after free due to a use after free. This could lead to local escalation of privilege 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 · high confidenceA use-after-free vulnerability exists in the lwis_process_transactions_in_queue function in lwis_transaction.c. The function accesses memory that has already been freed, creating a window for local privilege escalation. No user interaction is required for exploitation.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm the device runs Google AndroidCheck /proc/version or run 'getprop ro.build.id' or 'uname -a' to verify the operating system is AndroidAffected if The device is not running Google Android - this CVE only affects Android systems
-
Identify if the lwis kernel driver is presentCheck for the lwis driver module or device files - look for 'lwis' in /proc/modules, /sys/module/, or search kernel config for CONFIG_LWIS using 'zcat /proc/config.gz' or checking /boot/config-*Affected if The lwis driver is not present on the device - the vulnerability only applies when this specific driver is loaded
-
Check the Android kernel versionRun 'uname -r' or check /proc/version to obtain the kernel version, then compare against any available patch information from Android security bulletinsAffected if Running an unpatched Android kernel - the vulnerability exists in all versions of the lwis driver present in Android kernels
A device is affected if it runs Google Android and has the lwis kernel driver loaded, as the use-after-free flaw exists in all versions of this driver on Android platforms.
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 · scopedUpdate the kernel driver containing lwis_transaction.c to a version where the memory management in lwis_process_transactions_in_queue properly maintains object lifetime and does not access freed memory.
Android 14 (April 2024 security patch level) or later; Specific patch level: S1A24.04.00 / S2A24.04.00 or later depending on device
- 1. Navigate to Settings on your Android device
- 2. Tap on 'System' or 'About phone'
- 3. Select 'System update' or 'Software update'
- 4. Check for and install any available updates
- 5. Verify the device is running a patched Android version (April 2024 security patch level or later)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29787 — 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-29787 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