dbcve.org
AndroidOperating system · Google

CVE-2020-0404

MEDIUM · 5.5 CVSS v3.1 Published 2020-09-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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 uvc_scan_chain_forward of uvc_driver.c, there is a possible linked list corruption due to an unusual root cause. This could lead to local escalation of privilege in the kernel with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-111893654References: 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 linked list corruption vulnerability exists in the USB Video Class (UVC) driver function uvc_scan_chain_forward in uvc_driver.c within the Android kernel. This flaw allows a local attacker to escalate privileges to kernel level without requiring any additional execution privileges or user interaction.

MitigationApply the upstream kernel patch addressing the linked list handling in uvc_scan_chain_forward. Android devices require security updates from device manufacturers.

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
Communications Cloud Native Core Binding Support FunctionApplication
Affected:= 22.1.3
Communications Cloud Native Core Network Exposure FunctionApplication
Affected:= 22.1.1
Communications Cloud Native Core PolicyApplication
Affected:= 22.2.0

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Determine if the UVC (USB Video Class) driver is present
    Check for the uvcvideo kernel module: lsmod | grep uvcvideo or check /sys/module/uvcvideo exists. On Android, also check /dev/video* devices or camera functionality that relies on UVC.
    Affected if The UVC driver is loaded or built into the kernel (uvcvideo module present)
  2. Identify the kernel version
    Run 'uname -r' on Linux systems or check /proc/version. On Android, check via 'cat /proc/version' or in Settings > About Phone > Kernel version.
    Affected if The kernel version is older than the patched version containing the fix for uvc_scan_chain_forward in uvc_driver.c (linked list handling fix)
  3. Confirm Android version or Oracle product version
    On Android: Settings > About Phone > Android version. For Oracle products: check installed package version via product-specific CLI or config file.
    Affected if Running Google Android (any version without security update) OR Oracle Communications Cloud Native Core Binding Support Function = 22.1.3 OR Oracle Communications Cloud Native Core Network Exposure Function = 22.1.1 OR Oracle Communications Cloud Native Core Policy = 22.2.0
  4. Check security patch level on Android
    On Android: Settings > About Phone > Security patch level. This indicates whether the monthly security update containing the CVE fix has been applied.
    Affected if The Security patch level is earlier than the month the CVE-2020-0404 fix was released (typically January 2020 or later security patches)

A system is affected if it runs Android or the specific Oracle versions listed AND has the UVC driver loaded/present AND lacks the security update containing the linked list corruption fix in uvc_scan_chain_forward.

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 upstream kernel patch addressing the linked list handling in uvc_scan_chain_forward. Android devices require security updates from device manufacturers.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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