CVE-2022-50240 json
android: binder: stop saving a pointer to the VMA
published 2025-09-15 13 mo ago modified 2026-08-05 3 mo ago also EUVD-2022-55512
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
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.
[akpm@linux-foundation.org: fix drivers/android/binder_alloc_selftest.c]
Patch / fix
- Linux Linux 5.4.224, 5.10.154, 5.15.61, 5.18.18, 5.19.2, 6.0
- linux Debian 14, Debian 13, Debian 12 5.19.6-1
debian advisories DEBIAN-CVE-2022-50240
- git.kernel.org/stable/c/27a594bc7a7c8238d239e3cdbcf2edfa3bbe9a1b commit
- git.kernel.org/stable/c/015ac18be7de25d17d6e5f1643cb3b60bfbe859e commit
- git.kernel.org/stable/c/622ef885a89ad04cfb76ee478fb44f051125d1f1 commit
- git.kernel.org/stable/c/925e6b6f82c9c80ab3c17acbde8d16f349da7d26 commit
- git.kernel.org/stable/c/1ec3f76a436d750fd5023caec5da0494fc2870d2 commit
- git.kernel.org/stable/c/a43cfc87caaf46710c8027a8c23b8a55f1078f19 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-50240 updated
kernel: binder: fix UAF of alloc->vma in race with munmap()
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-416 Use After Free
- Technology feeds
References
-
git.kernel.org
/stable/c/27a594bc7a7c8238d239e3cdbcf2edfa3bbe9a1b
patch
-
git.kernel.org
/stable/c/015ac18be7de25d17d6e5f1643cb3b60bfbe859e
patch
-
git.kernel.org
/stable/c/622ef885a89ad04cfb76ee478fb44f051125d1f1
patch
-
git.kernel.org
/stable/c/925e6b6f82c9c80ab3c17acbde8d16f349da7d26
patch
-
git.kernel.org
/stable/c/1ec3f76a436d750fd5023caec5da0494fc2870d2
patch
-
git.kernel.org
/stable/c/a43cfc87caaf46710c8027a8c23b8a55f1078f19
patch
Sources
- CVE List CVE-2022-50240
- NVD CVE-2022-50240
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.