CVE-2022-20141
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 ip_check_mc_rcu of igmp.c, there is a possible use after free due to improper locking. This could lead to local escalation of privilege when opening and closing inet sockets with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-112551163References: Upstream 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 · high confidenceUse-after-free vulnerability in ip_check_mc_rcu function in igmp.c due to improper locking. The race condition allows local privilege escalation through opening and closing inet sockets without additional privileges. User interaction is not required.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/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 kernel versionOn the device, run 'uname -r' or check Settings > About Phone > Kernel Version to retrieve the running kernel versionAffected if The kernel version is older than the version that includes the CVE-2022-20141 patch (the patch was merged in Linux kernel 5.4.194, 5.10.114, 5.15.43, and later versions)
-
Check Android security patch levelGo to Settings > About Phone > Security Patch Level or run 'getprop ro.build.version.security_patch' to see the installed Android security updateAffected if The security patch level is earlier than the July 2022 Android security update which contains the fix for this vulnerability
-
Verify igmp.c source for proper lockingIf you have access to the kernel source for your device, examine the ip_check_mc_rcu function in net/ipv4/igmp.c and verify that the proper RCU locking is implemented to prevent the use-after-freeAffected if The function lacks proper rcu_read_lock() / rcu_read_unlock() pairs around the vulnerable code path
-
Check for available system updatesGo to Settings > System > Software Update or Settings > About Phone > Software Update to check if any updates are availableAffected if Updates are available that have not yet been installed on the device
A device is affected if it is running an Android kernel version or security patch level that predates the July 2022 Android security updates containing the fix for the ip_check_mc_rcu use-after-free vulnerability.
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 upstream kernel patch addressing the improper locking in ip_check_mc_rcu; Android users should apply available security updates.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20141 — 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-20141 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