CVE-2019-9275
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 a use after free due to improper locking. This could lead to escalation of privilege with System 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 Android kernel's mnh driver due to improper locking/synchronization. This memory corruption flaw can be exploited to escalate privileges from System-level access, potentially achieving higher-level system control without user 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
- 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 the target system is AndroidCheck for Android-specific files or properties: look for /system/build.prop, run 'getprop ro.build.version.sdk', or check /proc/version for 'Android' in the kernel stringAffected if System is not Android - this vulnerability is specific to Android kernel
-
Verify the mnh driver exists in the kernelCheck if the mnh driver is compiled into the kernel or available as a loadable module. Look for 'mnh' in /proc/kallsyms, or check kernel config if accessible via /boot/config-* or /proc/config.gzAffected if The mnh driver is not present in the kernel - the vulnerability only applies when this driver exists
-
Check if mnh driver is loaded or activeList loaded kernel modules with 'lsmod' and search for 'mnh', or check /sys/module/ for an 'mnh' directory, or inspect /dev/ for mnh device nodesAffected if The mnh driver module is loaded or the mnh device is present - this driver must be active for the use-after-free to be exploitable
-
Verify kernel version and patch statusRun 'uname -a' to get the kernel version, then cross-reference with Android security bulletin for CVE-2019-9275 to see if a patch has been applied. Check if the kernel source contains the locking fix in the mnh driver codeAffected if Kernel is unpatched for CVE-2019-9275 and the mnh driver is present - the vulnerability exists in all Android versions without the specific patch
A user is affected if the system runs Android with the mnh driver present and loaded, and the kernel lacks the CVE-2019-9275 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 the Android security patch for this kernel vulnerability. If no patch is available, consider disabling or removing the mnh driver if feasible, and ensure devices receive timely kernel/firmware updates from the OEM.
- Consultation8.0 h
- Implementation2.0 h
- Testing16.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,704.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9275 — 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-9275 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