CVE-2019-9274
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 possible out of bounds write due to a missing bounds check. This could lead to local 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 · moderate confidenceIn the Android kernel mnh driver, a missing bounds check allows an out of bounds write, enabling local privilege escalation to System level from an unspecified lower privilege context. This is a kernel-level vulnerability requiring no 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.
-
Verify if mnh driver is present in the kernelCheck /proc/config.gz (if available) or look for mnh-related kernel configuration options, or examine kernel modules with 'lsmod | grep mnh' if the driver is built as a loadable moduleAffected if The mnh driver is loaded or built into the running kernel and the device has not received the security patch that addresses this vulnerability
-
Check the Android security patch levelOn the device, go to Settings > About Phone > Build Number, or run 'getprop ro.build.version.security_patch' via ADB to retrieve the security patch dateAffected if The security patch level is earlier than the date when this vulnerability was patched (typically post-December 2019) or if the patch level cannot be determined
-
Determine the kernel versionRun 'uname -r' or check 'getprop ro.kernel.version' via ADB to identify the running kernel versionAffected if The kernel version is older and has not incorporated the mnh driver bounds check fix; compare against the version that includes the fix (if known) or against upstream kernel versions that contain the patch
-
Check if SELinux or other kernel protections are properly enforcingVerify SELinux status with 'getenforce' and check that kernel enforces mode is active; also verify if kernel lockdown mode is enabled if applicableAffected if Kernel security mechanisms are disabled or in a permissive state that would allow exploitation of the privilege escalation vector
-
Review system logs for mnh driver errorsExamine dmesg output or /proc/kmsg for any mnh-related kernel messages, out-of-bounds write errors, or memory corruption indicators related to the mnh driverAffected if The mnh driver is actively logging errors suggesting the vulnerable code path is being exercised
The device is likely affected if the mnh driver is present in the kernel and the device is running a kernel version or security patch level predating the CVE-2019-9274 fix.
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 kernel security updates that patch the mnh driver; verify that affected devices receive the kernel patch through OEM/firmware updates.
- Consultation4.0 h
- Implementation2.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 $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9274 — 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-9274 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