CVE-2022-20574
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 sec_sysmmu_info of drm_fw.c, there is a possible out of bounds read due to improper input validation. 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-237582191References: 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 sec_sysmmu_info function within drm_fw.c in the Android kernel's DRM subsystem. The function lacks proper input validation, allowing a local attacker to read kernel memory contents beyond intended boundaries, resulting in information disclosure.
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.
-
Identify the Android kernel versionRun 'uname -r' or check /proc/version to determine the running kernel version. Also check Android build number in Settings > About Phone > Android version.Affected if The kernel version is earlier than the version that includes the security patch containing the fix for CVE-2022-20574.
-
Verify the vulnerable source file existsCheck if the file drivers/gpu/drm/drm_fw.c exists in the kernel source tree or mounted debugfs. The function sec_sysmmu_info should be present in this file.Affected if The drm_fw.c file with the sec_sysmmu_info function is present in the kernel build.
-
Confirm DRM subsystem is enabledCheck /proc/config.gz (if available) or kernel configuration for CONFIG_DRM and related DRM framework options. The vulnerability exists within the DRM subsystem.Affected if The DRM subsystem (CONFIG_DRM) is compiled into the kernel, making the vulnerable code path executable.
-
Check if specific secure mmum (sysmmu) driver is loadedExamine loaded kernel modules via 'lsmod' and check for Samsung-specific or vendor DRM memory management modules that utilize sec_sysmmu_info.Affected if A vendor-specific DRM sysmmu driver that calls sec_sysmmu_info is active on the device.
A device is affected if it runs an unpatched Android kernel containing the drm_fw.c file with the sec_sysmmu_info function and has the DRM subsystem enabled.
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 patching the affected Android kernel version with updated source code that adds proper bounds checking and input validation to the sec_sysmmu_info function in drm_fw.c. Organizations should apply Android security updates as they become available.
- Consultation4.0 h
- Implementation8.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,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20574 — 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-20574 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