dbcve.org
AndroidOperating system · Google

CVE-2017-11030

HIGH · 7.8 CVSS v3.0 Published 2017-12-05
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 Android for MSM, Firefox OS for MSM, QRD Android, with all Android releases from CAF using the Linux kernel, in the HDMI video driver function hdmi_edid_sysfs_rda_res_info(), userspace can perform an arbitrary write into kernel memory.

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

Kernel arbitrary write vulnerability in the HDMI video driver's hdmi_edid_sysfs_rda_res_info() function used in Android devices based on CAF (Code Aurora Forum) releases. The function lacks proper bounds checking, allowing a local userspace attacker to write arbitrary data to kernel memory, potentially achieving privilege escalation.

MitigationApply the vendor security patch for CVE-2017-11030, which adds proper bounds checking in the hdmi_edid_sysfs_rda_res_info() function. Until patched, minimize exposure by restricting physical access and monitoring for suspicious kernel-level activity.

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. Confirm device runs Google Android
    Check /system/build.prop for 'ro.build.type=userdebug' or 'ro.build.type=eng', and verify 'ro.product.model' and 'ro.build.id' exist. Alternatively, check /proc/version for kernel build information indicating Android.
    Affected if The device is a Google Android-based device (including custom ROMs based on CAF releases).
  2. Identify HDMI driver module presence
    Check /proc/modules or lsmod for hdmi-related kernel modules. Look for modules containing 'hdmi', 'edid', 'mdss', or 'display' in their names. Also check /sys/class/drm for HDMI connector entries.
    Affected if The HDMI/display subsystem modules are loaded, making the hdmi_edid_sysfs_rda_res_info() code path potentially reachable.
  3. Locate the EDID sysfs interface
    Search for edid-related files in /sys/class/drm/*/edid or /sys/devices/virtual/graphics/fb*/edid. List contents of /sys/class/drm to identify HDMI-related device nodes.
    Affected if The sysfs EDID interface exists, meaning the vulnerable hdmi_edid_sysfs_rda_res_info() function can be invoked through /sys/class/drm/.../edid or similar paths.
  4. Verify kernel version against patched releases
    Check 'uname -r' or /proc/version. Compare against known CAF release kernel versions. Since Android all versions are affected, look for any security patch level in /system/build.prop under 'ro.build.version.security_patch'.
    Affected if The kernel security patch level predates the CVE-2017-11030 fix date (approximately mid-2017), indicating the bounds checking may not yet be implemented.

A user is affected if the device runs Google Android with the HDMI/EDID subsystem present and accessible through sysfs, and the kernel security patch level is older than the CVE-2017-11030 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 vendor security patch for CVE-2017-11030, which adds proper bounds checking in the hdmi_edid_sysfs_rda_res_info() function. Until patched, minimize exposure by restricting physical access and monitoring for suspicious kernel-level activity.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-11030 — 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-2017-11030 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