CVE-2022-50240 Details
Description
In the Linux kernel, the following vulnerability has been resolved: android: binder: stop saving a pointer to the VMA Do not record a pointer to a VMA outside of the mmap_lock for later use. This is unsafe and there are a number of failure paths *after* the recorded VMA pointer may be freed during setup. There is no callback to the driver to clear the saved pointer from generic mm code. Furthermore, the VMA pointer may become stale if any number of VMA operations end up freeing the VMA so saving it was fragile to being with. Instead, change the binder_alloc struct to record the start address of the VMA and use vma_lookup() to get the vma when needed. Add lockdep mmap_lock checks on updates to the vma pointer to ensure the lock is held and depend on that lock for synchronization of readers and writers - which was already the case anyways, so the smp_wmb()/smp_rmb() was not necessary. [[email protected]: fix drivers/android/binder_alloc_selftest.c]
A use-after-free vulnerability has been identified in the Linux kernel's binder component, specifically in stable branches 5.4 and 5.10. The issue arises from a race condition between the 'munmap' function and the 'binder_update_page_range' function, which can lead to accessing a freed memory area. This vulnerability was introduced when the 'munmap' function was modified to detach virtual memory areas (VMAs) with only a read lock, allowing the VMA to be freed while still being accessed by the binder, creating the potential for a use-after-free condition.
Users can upgrade to the latest version of the Linux kernel to address this vulnerability. Instructions for downloading the latest kernel version can be found on the official Linux kernel website.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/015ac18be7de25d17d6e5f1643cb3b60bfbe859e | kernel.org | Patch |
| https://git.kernel.org/stable/c/1ec3f76a436d750fd5023caec5da0494fc2870d2 | kernel.org | Patch |
| https://git.kernel.org/stable/c/27a594bc7a7c8238d239e3cdbcf2edfa3bbe9a1b | kernel.org | Patch |
| https://git.kernel.org/stable/c/622ef885a89ad04cfb76ee478fb44f051125d1f1 | kernel.org | Patch |
| https://git.kernel.org/stable/c/925e6b6f82c9c80ab3c17acbde8d16f349da7d26 | kernel.org | Patch |
| https://git.kernel.org/stable/c/a43cfc87caaf46710c8027a8c23b8a55f1078f19 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-416 | Use After Free | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 4.20, < 5.4.224 >= 5.5, < 5.10.154 >= 5.11, < 5.15.61 >= 5.16, < 5.18.18 >= 5.19, < 5.19.2 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Aug 4, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 24, 2025 | Initial Analysis | [email protected] |
| Oct 10, 2025 | CVE Modified | kernel.org |
| Sep 15, 2025 | New CVE Received | kernel.org |