CVE-2024-22010
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 dvfs_plugin_caller of fvp.c, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
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 missing bounds check in the dvfs_plugin_caller function of fvp.c allows an out of bounds read, enabling local information disclosure without requiring elevated privileges or 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= 13.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
- 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.
-
Verify Android version is 13.0Run 'getprop ro.build.version.release' or check Settings > About Phone > Android versionAffected if The version shown is exactly 13.0 (not 13.0.x, not 14 or higher)
-
Identify fvp component presenceSearch for fvp.c or fvp-related binaries/libraries on the device using 'find / -name "*fvp*" 2>/dev/null' or check /system/lib64/Affected if Any fvp binary, library, or kernel module containing the dvfs_plugin_caller function is found on the device
-
Check dvfs_plugin_caller functionIf fvp component exists, examine it with 'strings' or disassemble to locate the dvfs_plugin_caller functionAffected if The dvfs_plugin_caller function is present and accessible without root privileges
-
Confirm information disclosure accessAttempt to trigger the dvfs_plugin_caller function with controlled input to verify out-of-bounds read capabilityAffected if The function can be invoked by a local unprivileged process and returns data beyond the intended buffer boundaries
A user is affected if their device runs Android exactly version 13.0 AND contains the fvp component with the vulnerable dvfs_plugin_caller function that can be triggered for out-of-bounds reads.
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.
dbcve · scopedAdd proper bounds validation before array access in the dvfs_plugin_caller function to prevent out of bounds reads.
Android 13.0 with subsequent security patch levels (consult Android Security Bulletin for specific fixed version)
- Check the Android Security Bulletin for CVE-2024-22010 to identify the specific Android Security Patch Level that contains the fix
- Apply the latest available Android security update for Android 13.0 through system settings or your device manufacturer's update channel
- Verify the installed Android Security Patch Level has been updated to a version that includes the fix for this vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22010 — 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-2024-22010 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