Vulnerability in Kernel: binder: fix async_free_space accounting for empty parcels
Summary
GSD-2022-1000024: binder: fix async_free_space accounting for empty parcels. Affects Kernel versions >= 74310e06be4d74dcf67cd108366710dee5c576d5, < 7c7064402609aeb6fb11be1b4ec10673ff17b593. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The Kernel is a critical component of the Linux operating system that manages system resources and facilitates communication between hardware and software. It provides essential functionalities for the proper functioning of the system. The binder subsystem within the Kernel is responsible for inter-process communication (IPC) between different components of the system. It allows processes to exchange data and messages efficiently. However, a vulnerability has been identified in the binder subsystem that affects the accounting of free space for empty parcels.
Vulnerability Detail
The vulnerability in the binder subsystem of the Kernel impacts the accounting of free space for empty parcels. When handling empty parcels, the async_free_space function fails to correctly account for the space freed, leading to potential memory corruption or resource exhaustion. An attacker could exploit this vulnerability to cause a denial-of-service (DoS) condition or potentially execute arbitrary code with elevated privileges. The vulnerability was introduced in version v4.14 of the Linux Kernel and has been fixed in version v4.19.224.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a workaround, users can apply the patch manually to their Kernel version. The patch can be obtained from the official Git repository and applied following the provided instructions. However, it is strongly advised to update to the fixed version rather than relying on a workaround.
Conclusion
The vulnerability in the binder subsystem of the Kernel, which affects the accounting of free space for empty parcels, can lead to memory corruption, resource exhaustion, and potential code execution with elevated privileges. It is crucial to update the Linux Kernel to version v4.19.224 or later to mitigate this vulnerability. Users can also use the Vulert Playground at https://vulert.com/scanner to check if their system is affected and receive real-time alerts for open-source vulnerabilities. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to memory corruption or resource exhaustion, potentially resulting in a denial-of-service (DoS) condition or arbitrary code execution with elevated privileges.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) and Vulert will provide real-time alerts for open-source vulnerabilities.
At the time of this report, there is no known exploit for this vulnerability. However, it is crucial to apply the fix promptly to mitigate any potential risks.
This vulnerability requires local access to the system to exploit. It cannot be exploited remotely over a network.
If you cannot immediately update the Kernel, you can apply the provided patch manually. However, it is strongly recommended to update to the fixed version as soon as possible.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
