CVE-2022-42528
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 ffa_mrd_prot of shared_mem.c, there is a possible ID due to a logic error in the code. 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-242203672References: 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 · moderate confidenceA logic error in the ffa_mrd_prot function in shared_mem.c within the Android kernel's ARM Firmware Framework for Android (FF-A) implementation allows local information disclosure. The vulnerability stems from incorrect conditional logic handling memory region descriptors that could expose sensitive data to unprivileged local attackers.
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 device runs Google AndroidCheck /system/build.prop for 'ro.build.version.sdk' or run 'getprop ro.product.model' to verify the device is an Android deviceAffected if Device is not running Google Android - other Linux distributions are not affected by this specific CVE
-
Check if kernel has FF-A support enabledReview kernel configuration (kernel config or /proc/config.gz) for CONFIG_ARM_FFA_INTERFACE or grep for 'ffa_' in kernel boot logs to see if the FF-A driver is loadedAffected if FF-A support is not enabled in the kernel - the vulnerability only exists in kernels with the ARM Firmware Framework for Android implemented
-
Verify ffa_mrd_prot function exists in kernelSearch the kernel source or System.map for the symbol 'ffa_mrd_prot' - if the function is present, the vulnerable code path existsAffected if The ffa_mrd_prot function is not present in the kernel - the vulnerability cannot be triggered without this function
-
Check if patch A-242203672 is appliedReview kernel source changes for shared_mem.c, looking for the fix to the conditional logic in ffa_mrd_prot that properly validates memory region descriptorsAffected if The specific fix for the logic error in ffa_mrd_prot is not present - the incorrect conditional logic that could expose sensitive data remains unpatched
A defender is affected if the device runs Google Android with FF-A support enabled and the kernel source does not contain the A-242203672 fix for the logic error in ffa_mrd_prot.
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 patch for A-242203672 to fix the logic error in ffa_mrd_prot. Since this is a kernel-level fix, ensure the patch is integrated into the Android kernel build and deployed via firmware OTA update.
- 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-42528 — 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-42528 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