dbcve.org
AndroidOperating system · Google

CVE-2019-2024

HIGH · 7.8 CVSS v3.0 Published 2019-06-19
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 em28xx_unregister_dvb of em28xx-dvb.c, there is a possible use after free issue. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-111761954References: Upstream kernel

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 confidence

A use-after-free vulnerability exists in the em28xx_unregister_dvb function within the em28xx-dvb.c driver (USB video capture device driver) in the Android kernel. The vulnerability allows a local attacker to achieve privilege escalation without requiring user interaction or additional execution privileges, due to memory being accessed after being freed.

MitigationApply the latest Android security patch (which includes the upstream kernel fix for this vulnerability). For custom/embedded Android implementations, obtain the upstream kernel patch and rebuild the kernel with the corrected em28xx driver 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
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.0/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. Check if the em28xx driver is present in the kernel
    Look for the em28xx-dvb.c driver file in the kernel source tree or check /sys/module/ for em28xx-related modules. On Android, examine /proc/kallsyms or /boot/config-[version] for CONFIG_VIDEO_EM28XX settings.
    Affected if The em28xx driver is compiled into the kernel or loaded as a module (any presence indicates potential exposure).
  2. Identify the kernel version
    Run 'uname -r' or check /proc/version to retrieve the running kernel version string.
    Affected if The device is running any version of the Android kernel (all versions are affected per the CVE).
  3. Check for USB video capture device usage
    Inspect /sys/bus/usb/devices/ or run 'lsusb' to enumerate connected USB devices. Look for em28xx-based USB video capture devices (often listed as em28xx chipset or generic USB video class devices).
    Affected if A USB video capture device using the em28xx chipset is connected or has been used on the device.
  4. Review kernel logs for use-after-free indicators
    Examine dmesg output or /var/log/kern.log for memory corruption errors, kernel panics, or oops messages referencing 'em28xx', 'dvb', or 'use-after-free' patterns.
    Affected if Any crash or memory error logs involving the em28xx driver are found.
  5. Verify Android security patch level
    Check the Android system settings under 'About phone > Security patch level' or run 'getprop ro.build.version.security_patch' to obtain the installed security patch date.
    Affected if The security patch level is earlier than the patch date that includes the fix for this CVE (the fix is incorporated in Android security updates).

A user is affected if the device runs any Android version with the em28xx USB video capture driver present and the security patch level predates the fix.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the latest Android security patch (which includes the upstream kernel fix for this vulnerability). For custom/embedded Android implementations, obtain the upstream kernel patch and rebuild the kernel with the corrected em28xx driver code.

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-2019-2024 — 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-2019-2024 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