Memory Corruption Vulnerability in Android Memory Management Driver - ASB-A-185195266

:unknown: Updated 02 Oct 2025

Summary

01/06/2021
High
Yes i
High
Not published

ASB-A-185195266: In memory management driver, there is a possible memory corruption due to a double free. Affects :unknown: versions >= SoCVersion:0, < SoCVersion:2021-06-05. Fixed in SoCVersion:2021-06-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 Your last release was probably never penetration tested 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 memory management driver is a critical component of the Android operating system, responsible for managing memory allocation and deallocation for applications and system processes. It ensures efficient memory usage and stability of the system. However, this driver is susceptible to vulnerabilities that can lead to security risks, such as privilege escalation.

Vulnerability Detail

The vulnerability identified as ASB-A-185195266 involves a memory corruption issue due to a double free error in the memory management driver. This flaw can allow an attacker to escalate privileges locally without requiring additional execution privileges. The vulnerability arises from improper handling of memory deallocation, which can lead to unpredictable behavior and potential exploitation by malicious actors.

How To Fix

Minimum fixed version

SoCVersion:2021-06-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 to mitigate this vulnerability other than applying the necessary updates to the system software.

Conclusion

The ASB-A-185195266 vulnerability in the Android memory management driver poses a significant risk due to its potential for local privilege escalation. It is crucial for users to update their devices to the latest software version to mitigate this risk. Regular monitoring for vulnerabilities, such as through tools like Vulert, can further enhance security.

See every vulnerability recorded for :unknown: →

Share this vulnerability

FAQ

A double free vulnerability occurs when a program attempts to free the same memory location more than once, leading to memory corruption and potential exploitation.

An attacker can exploit this vulnerability to escalate their privileges on the device, potentially gaining unauthorized access to sensitive information or system functions.

No, user interaction is not needed for exploitation, making this vulnerability particularly concerning.

If your device is affected, ensure that you update to the latest software version provided by your device manufacturer to patch the vulnerability.

Vulert uses the gradle.lockfile to monitor and alert in real-time for open-source vulnerabilities in software, allowing developers to stay informed about potential security risks.

Related vulnerabilities

Recent vulnerabilities recorded for :unknown:.

How To Fix

Minimum fixed version

SoCVersion:2021-06-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