Linux KernelOperating system · Linux
CVE-2022-20105
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 MM service, there is a possible out of bounds write due to a stack-based buffer overflow. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: DTV03330460; Issue ID: DTV03330460.
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 confidenceA stack-based buffer overflow exists in the MM (Multimedia) service, allowing an attacker with System execution privileges to write beyond buffer boundaries. This memory corruption can lead to local privilege escalation. The vulnerability does not require 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 data
Linux KernelOperating system
= 4.9= 4.19= 9.0= 10.0= 11.0CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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.
-
Identify the Linux kernel versionRun `uname -r` or check `/proc/version` to determine the installed kernel versionAffected if The kernel version is exactly 4.9.x or 4.19.x (e.g., 4.9.0, 4.9.123, 4.19.0, 4.19.88)
-
Identify the Android versionRun `getprop ro.build.version.release` on the device or check Settings > About Phone > Android versionAffected if The Android version is 9.0, 10.0, or 11.0
-
Verify the MM (Multimedia) service is presentCheck for multimedia-related processes or services running on the system using `ps | grep -i mm` or `ps | grep -i multimedia`Affected if The MM service process is found running on the system (vulnerable code path exists)
-
Confirm the patch DTV03330460 is not appliedCheck system logs, vendor documentation, or kernel config for references to patch DTV03330460; compare the MM service binary against a patched version if availableAffected if No evidence of patch DTV03330460 is found and the kernel/Android version falls within the affected ranges
The environment is affected if it runs Linux Kernel 4.9 or 4.19, or Android 9.0/10.0/11.0, has the MM service active, and lacks the DTV03330460 patch.
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 patch DTV03330460 to the MM service, which addresses the bounds checking issue in the vulnerable code path. Verify the fix through regression testing of multimedia functionality.
Fix this in Linux Kernel
Scoped from the published advisory
- Consultation6.0 h
- Implementation8.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20105 — 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-20105 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