High · published September 15, 2025
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]
| Product | Versions | Fixed in |
|---|---|---|
| linux/linux_kernel | ≥ 4.20, < 5.4.224 | 5.4.224 |
| linux/linux_kernel | ≥ 5.5, < 5.10.154 | 5.10.154 |
| linux/linux_kernel | ≥ 5.11, < 5.15.61 | 5.15.61 |
| linux/linux_kernel | ≥ 5.16, < 5.18.18 | 5.18.18 |
| linux/linux_kernel | ≥ 5.19, < 5.19.2 | 5.19.2 |