binder: fix race between mmput() and do_exit()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 · < 67f16bf2cc1698fd50e01ee8a2becc5a8e6d3a3e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
binder: fix race between mmput() and do_exit()
Task A calls binder_update_page_range() to allocate and insert pages on a remote address space from Task B. For this, Task A pins the remote mm via mmget_not_zero() first. This can race with Task B do_exit() and the final mmput() refcount decrement will come from Task A.
Task A | Task B ------------------+------------------ mmget_not_zero() | | do_exit() | exit_mm() | mmput() mmput() | exit_mmap() | remove_vma() | fput() |
In this case, the work of ____fput() from Task B is queued up in Task A as TWA_RESUME. So in theory, Task A returns to userspace and the cleanup work gets executed. However, Task A instead sleep, waiting for a reply from Task B that never comes (it's dead).
This means the binder_deferred_release() is blocked until an unrelated binder event forces Task A to go back to userspace. All the associated death notifications will also be delayed until then.
In order to fix this use mmput_async() that will schedule the work in the corresponding mm->async_put_work WQ instead of Task A.
From the CVE record · Linux
A race between mmput() and do_exit() in the Linux kernel's binder component can block deferred release and delay associated death notifications. It occurs when one task pins another task's address space while that task exits; the waiting task may not return to userspace to run cleanup until an unrelated binder event occurs.
Engineers running Linux kernels with binder should check their versions against the vendor advisory; affected versions were not provided.