CVE-2022-20585
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 valid_out_of_special_sec_dram_addr of drm_access_control.c, there is a possible EoP due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-238716781References: 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 confidenceA local privilege escalation vulnerability exists in the Android kernel's DRM access control mechanism. The function valid_out_of_special_sec_dram_addr in drm_access_control.c fails to properly validate input, allowing a local attacker to escalate privileges without user interaction. This is a kernel-level flaw affecting Android kernel components.
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
- High
- Availability
- High
CVSS:3.1/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 checksWork through these to decide whether this CVE applies to you.
-
Check Android Security Patch LevelGo to Settings > About Phone > Security Patch Level (or Settings > System > Security > Security Patch Level on newer Android versions). Record the date shown.Affected if The Security Patch Level is earlier than February 2022, as the fix was released in the Android Security Bulletin for that month.
-
Identify the kernel versionOn the device, use a terminal app or ADB to run 'uname -a' or check Settings > About Phone > Kernel Version. Record the full version string.Affected if The kernel version predates the February 2022 Android Security update and the patch for this CVE has not been applied.
-
Verify the drm_access_control.c patch statusIf you have access to the kernel source or a rooted device, locate the file drivers/gpu/drm/drm_access_control.c and check the function valid_out_of_special_sec_dram_addr for proper bounds checking on the input parameters.Affected if The function lacks proper validation checks for the input address parameters, allowing out-of-bounds memory access.
-
Confirm DRM kernel module is loadedOn a rooted device or through ADB, run 'lsmod' or check /proc/modules for drm-related modules. Also check /sys/module/drm/ for module presence.Affected if The vulnerable DRM access control code is active and the device is running an unpatched kernel version.
A device is affected if it runs an Android kernel version with a Security Patch Level before February 2022, or if the drm_access_control.c source code lacks proper input validation in the valid_out_of_special_sec_dram_addr function.
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 dataApply the vendor-provided kernel security patch for Android that addresses the input validation issue in drm_access_control.c. This typically involves updating the affected kernel version with the CVE fix from the Android Security Bulletin.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20585 — 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-20585 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