CVE-2019-9442
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 the Android kernel in the mnh driver there is possible memory corruption due to a use after free. This could lead to local escalation of privilege with System privileges required. 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 confidenceUse-after-free vulnerability in the Android kernel's mnh driver allows memory corruption, potentially enabling local privilege escalation from System privileges. The vulnerability stems from improper memory management in the driver, likely during device initialization or data handling routines.
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
- 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.
-
Confirm mnh driver presenceCheck if the mnh driver is present on the device by searching for mnh-related device nodes in /dev/ or checking /sys/class for mnh entries (e.g., ls /sys/class/ | grep -i mnh)Affected if The mnh driver device nodes or sysfs entries exist on the device
-
Identify mnh driver moduleCheck if the mnh.ko kernel module is loaded by running 'lsmod' or checking /proc/modules, or look for mnh in /sys/module/Affected if The mnh kernel module is loaded in memory
-
Verify patch applicationCheck the Android security patch level in Settings > About Phone > Security Patch Level, or retrieve via 'getprop ro.build.version.security_patch' commandAffected if The Security Patch Level is earlier than the May 2019 Android Security Bulletin (the month CVE-2019-9442 was addressed)
-
Confirm driver is in useCheck if any processes are actively using the mnh driver by examining /proc/<pid>/fd or checking for mnh in /proc/interrupts if it's a hardware driverAffected if The mnh driver is actively accessed or handles interrupts on the device
A user is affected if the mnh driver is present/loaded on their Android device AND the device has not received the May 2019 or later Android security patch.
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 Android security patches released by the device vendor or Google (via monthly security bulletin). Since this is a kernel driver issue, OTA system updates are the primary remediation vector.
- Consultation4.0 h
- Testing6.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 $3,584.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9442 — 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-2019-9442 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