CVE-2024-34748: Android Device Memory Server Use-After-Free Vulnerability

:unknown: Updated 02 Oct 2025

Summary

01/10/2024
Yes i
High
Not published

CVE-2024-34748: In _DevmemXReservationPageAddress of devicemem_server.c, there is a possible use-after-free due to improper casting. Affects :unknown: versions >= SoCVersion:0, < SoCVersion:2024-10-05. Fixed in SoCVersion:2024-10-05. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Android Device Memory Server is a crucial component in the Android ecosystem, responsible for managing device memory resources. It facilitates communication between applications and the underlying hardware, ensuring efficient memory allocation and usage. However, it is susceptible to vulnerabilities that can lead to security risks, such as privilege escalation.

Vulnerability Detail

In the Android Device Memory Server, specifically in the _DevmemXReservationPageAddress function of devicemem_server.c, a use-after-free vulnerability exists due to improper casting. This flaw allows an attacker to exploit the vulnerability to escalate privileges within the kernel without requiring additional execution privileges. The vulnerability is particularly concerning as it can be exploited locally, posing a significant security risk to the system.

How To Fix

Minimum fixed version

SoCVersion:2024-10-05

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

Currently, there are no specific workarounds available for this vulnerability. The best course of action is to apply the patch as soon as it becomes available.

Conclusion

The CVE-2024-34748 vulnerability poses a significant risk to the Android Device Memory Server, allowing for potential local privilege escalation. Users are strongly advised to update their systems to the latest patched version to mitigate this risk. Regular monitoring and updates are crucial for maintaining system security.

See every vulnerability recorded for :unknown: →

Share this vulnerability

FAQ

CVE-2024-34748 is a vulnerability in the Android Device Memory Server that allows for local privilege escalation due to a use-after-free error.

You can check if your application is affected by using the Vulert playground at Vulert Scanner, which monitors open-source vulnerabilities without requiring any signup.

If your device is vulnerable, you should update to the patched version of the Android Device Memory Server released on October 5, 2024.

The primary risk is local privilege escalation, which could allow an attacker to gain unauthorized access to system resources and potentially compromise the device's security.

No, user interaction is not needed for exploitation, making it particularly dangerous.

Related vulnerabilities

Recent vulnerabilities recorded for :unknown:.

How To Fix

Minimum fixed version

SoCVersion:2024-10-05

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback