CVE-2022-20575
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 read_ppmpu_info of drm_fw.c, there is a possible out of bounds read due to an incorrect bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-237585040References: N/A
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 confidenceAn out-of-bounds read vulnerability exists in the read_ppmpu_info function of drm_fw.c in the Android kernel. The issue stems from an incorrect bounds check that allows reading memory beyond intended boundaries, potentially exposing sensitive information from kernel memory to a local attacker without requiring elevated privileges or 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Confirm the device runs Google AndroidCheck /proc/version or run 'uname -a' to see if the kernel is an Android kernel (look for 'Android' in the version string)Affected if The system is not running a Google Android kernel, as the vulnerability exists only in Android kernel implementations of drm_fw.c
-
Identify the kernel versionRun 'cat /proc/version' or 'uname -r' to obtain the kernel version stringAffected if The device runs any version of Google Android kernel, as the advisory states all versions are affected
-
Check if the drm_fw kernel module or driver is presentLook for drm_fw related files in /sys/module/ or check kernel config for CONFIG_DRM_FW (run 'ls /sys/module/ | grep -i drm' or check /boot/config-* for DRM_FW configuration)Affected if The drm_fw module is loaded or built into the kernel, as the vulnerability exists in the read_ppmpu_info function of drm_fw.c
-
Verify the read_ppmpu_info function is accessibleIf kernel source is available, inspect drm_fw.c for the read_ppmpu_info function and check the bounds check logic around array index validationAffected if The function exists and processes PPMPU data without proper boundary validation, indicating the vulnerable code path is present
A user is affected if the device runs any version of Google Android with the drm_fw component present and the vulnerable read_ppmpu_info function accessible, as all Android versions are impacted by this out-of-bounds read.
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 dataThis kernel-level vulnerability requires a code fix in the drm_fw.c file to correct the bounds check logic in the read_ppmpu_info function. The fix should validate array indices against proper boundary limits before memory access operations.
- Consultation4.0 h
- Implementation6.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 $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20575 — 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-2022-20575 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