CVE-2024-32910
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 handle_msg_shm_map_req of trusty/user/base/lib/spi/srv/tipc/tipc.c, there is a possible stack data disclosure due to uninitialized data. 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 confidenceIn handle_msg_shm_map_req within the trusty TEE component (tipc.c), uninitialized stack data can be disclosed due to a buffer not being properly initialized before use. This allows 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 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 if the device uses Trusty TEECheck if /vendor/bin/hw/tee or /system/bin/tee directories exist, or look for 'trusty' in /proc/mounts or kernel cmdline parameters. Some Android devices expose TEE info via 'dmesg | grep -i trusty' or 'ls /dev/block/bootdevice/by-name' containing 'trust' partitions.Affected if The device does not use Trusty TEE - this vulnerability only applies to devices with Trusty TEE implemented.
-
Determine the Android versionRun 'getprop ro.build.version.release' or check Settings > About Phone > Android version.Affected if Any Android version is listed as affected, so all Android devices with Trusty TEE are potentially impacted.
-
Check if TEE shm_map functionality is accessibleLook for tipc-related kernel modules or services: 'ls /sys/firmware/devicetree/base/compatible' 2>/dev/null | grep -i tipc, or check for 'shm_map' references in any TEE-related logs or configuration files in /vendor/etc or /system/etc.Affected if The device uses Trusty TEE with tipc (Trusted IPC) and shm_map functionality present - this is where the vulnerable handle_msg_shm_map_req function is called.
-
Inspect tipc.c source if availableIf you have root access and the source is available, locate tipc.c in the trusty component and search for 'handle_msg_shm_map_req' function. Verify whether the buffer variable used in this function is initialized before use.Affected if The function handle_msg_shm_map_req exists and contains a buffer that is NOT properly initialized before use - this is the vulnerable code path.
A user is affected if their Android device implements Trusty TEE with the tipc component, since the vulnerability exists in the handle_msg_shm_map_req function within tipc.c where uninitialized stack buffers can leak memory contents.
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 dataProperly initialize stack buffers in the handle_msg_shm_map_req function before use to prevent leakage of uninitialized memory contents. Apply the vendor patch when available.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-32910 — 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-32910 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