dbcve.org
AndroidOperating system · Google

CVE-2022-42775

MEDIUM · 5.5 CVSS v3.1 Published 2022-12-06
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 camera driver, there is a possible memory corruption due to improper locking. 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

A race condition in the camera driver causes memory corruption due to improper locking mechanisms. The vulnerability allows a local attacker to trigger a denial of service by exploiting the unlocked memory access path in the kernel's camera subsystem.

MitigationApply the vendor-supplied kernel patch for the camera driver that implements proper locking; until then, restrict local untrusted code execution and monitor for kernel panics related to camera operations.

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. Verify Android version
    Check the device settings or run 'getprop ro.build.version.release' to confirm the Android OS version
    Affected if The version is 10.0, 11.0, or 12.0 - these are the only affected versions listed
  2. Identify camera driver in use
    Check /proc/modules or lsmod for camera-related kernel modules; on Android, examine /vendor/lib/modules/ for camera driver files
    Affected if A camera driver module is loaded and the device runs an affected Android version
  3. Confirm camera subsystem is active
    Check if camera services are running via 'dumpsys camera' or verify /dev/video* or /dev/media* device nodes exist
    Affected if Camera hardware is accessible and the Android version falls within the affected range
  4. Review kernel logs for camera-related issues
    Examine dmesg or logcat for messages containing 'camera', 'mm_camera', or 'isp' related errors, crashes, or memory corruption indicators
    Affected if Kernel panic or memory corruption logs reference camera subsystem and Android version is 10, 11, or 12

The device is affected only if it runs Android 10.0, 11.0, or 12.0 AND has an active camera driver - both conditions must be true.

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-supplied kernel patch for the camera driver that implements proper locking; until then, restrict local untrusted code execution and monitor for kernel panics related to camera operations.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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