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

:unknown: Updated 02 Oct 2025

Summary

01/05/2021
High
Yes i
High
Not published

ASB-A-183461320: In memory management driver, there is a possible memory corruption due to a use after free. Affects :unknown: versions >= SoCVersion:0, < SoCVersion:2021-05-05. Fixed in SoCVersion:2021-05-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 various applications and services. It ensures efficient memory usage, which is vital for system stability and performance. However, this driver is susceptible to a specific vulnerability that can lead to significant security risks.

Vulnerability Detail

The vulnerability identified as ASB-A-183461320 is a use-after-free memory corruption issue within the memory management driver. This flaw arises when the system attempts to access memory that has already been freed, potentially allowing an attacker to manipulate memory contents. The consequences of this vulnerability include local escalation of privilege, enabling unauthorized access to system resources without requiring additional execution privileges. Exploitation does not necessitate user interaction, making it particularly dangerous.

How To Fix

Minimum fixed version

SoCVersion:2021-05-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 available patch by updating the system.

Conclusion

The memory corruption vulnerability in the Android memory management driver poses a significant security risk, allowing for local privilege escalation without user interaction. It is crucial for users to update their systems to the patched version to protect against potential exploitation.

See every vulnerability recorded for :unknown: →

Share this vulnerability

FAQ

A use-after-free vulnerability occurs when a program continues to use a pointer after the memory it points to has been freed, potentially leading to memory corruption and exploitation.

An attacker can exploit this vulnerability by manipulating the memory after it has been freed, allowing them to execute arbitrary code or escalate privileges on the affected system.

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

If your device is affected, you should immediately update to the patched version of the Android operating system to mitigate the risk.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

Related vulnerabilities

Recent vulnerabilities recorded for :unknown:.

How To Fix

Minimum fixed version

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