dbcve.org
AndroidOperating system · Google

CVE-2022-39118

MEDIUM · 5.5 CVSS v3.1 Published 2023-01-04
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 sprd_sysdump driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial of service in 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 · moderate confidence

The sprd_sysdump driver (Spreadtrum system dump driver) contains an out-of-bounds write vulnerability caused by a missing bounds check. An attacker with local access could trigger this vulnerability to write beyond allocated buffer boundaries, leading to kernel denial of service. The vulnerability stems from insufficient input validation in the driver code.

MitigationApply vendor patches for the kernel and sprd_sysdump driver to add proper bounds checking. Until the patch is available, restrict local unprivileged access to prevent exploitation of this vulnerability.

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:= 10.0= 11.0= 12.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. Check Android version
    Run 'getprop ro.build.version.release' or check Settings > About Phone > Android version
    Affected if Version is 10.0, 11.0, or 12.0
  2. Identify device chipset vendor
    Check /proc/cpuinfo for 'Hardware' or 'model' field, or run 'getprop ro.hardware' or 'cat /sys/devices/soc0/soc_id'
    Affected if Hardware/chipset is Spreadtrum or SPRD (e.g., 'sprd' or 'Spreadtrum' appears in the output)
  3. Verify sprd_sysdump driver presence
    Check if driver exists in kernel: 'ls -la /dev/sprd_*' or 'grep -i sprd_sysdump /proc/kallsyms' or check /sys/module for 'sprd_sysdump'
    Affected if The sprd_sysdump driver module or device node is present on the system
  4. Check if driver is loaded or active
    Run 'lsmod' to list loaded modules and look for 'sprd_sysdump', or check 'dmesg | grep -i sprd_sysdump' for driver initialization messages
    Affected if The driver is loaded and initialized in memory

The environment is affected if running Android 10.0, 11.0, or 12.0 on Spreadtrum hardware with the sprd_sysdump driver present and loaded.

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 vendor patches for the kernel and sprd_sysdump driver to add proper bounds checking. Until the patch is available, restrict local unprivileged access to prevent exploitation of this vulnerability.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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