binder: fix race between mmput() and do_exit()
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 4.19.306, 5.10.209, 5.15.148, 5.4.268, 6.1.75, 6.6.14, 6.7.2
- CVEs
- CVE-2023-52609
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 6 Nov 2026, 17:59 UTC · Revision 1
Source evidence
binder: fix race between mmput() and do_exit()
core-osv · Original sourcePublished 18 Mar 2024, 10:07 UTC
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.
osv:CVE-2023-52609
Kernel
Fixed versions: 4.19.306, 5.4.268, 5.10.209, 5.15.148, 6.1.75, 6.6.14, 6.7.2
Complete source record
{
"id": "f489fcb8968f4c852db81fc89c080d59f3adaa9c66b86fa318d3c954a11edf2f",
"url": "https://osv.dev/vulnerability/CVE-2023-52609",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "binder: fix race between mmput() and do_exit()",
"summary": "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.",
"evidence": "osv:CVE-2023-52609",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "4.19.306",
"evidence": "/affected/1/ranges"
},
{
"value": "5.4.268",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.209",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.148",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.75",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.14",
"evidence": "/affected/1/ranges"
},
{
"value": "6.7.2",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2023-52609",
"aliases": [
"CVE-2023-52609"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "457b9a6f09f011ebcb9b52cc203a6331a6fc2de7"
},
{
"fixed": "95b1d336b0642198b56836b89908d07b9a0c9608"
},
{
"fixed": "252a2a5569eb9f8d16428872cc24dea1ac0bb097"
},
{
"fixed": "7e7a0d86542b0ea903006d3f42f33c4f7ead6918"
},
{
"fixed": "98fee5bee97ad47b527a997d5786410430d1f0e9"
},
{
"fixed": "6696f76c32ff67fec26823fc2df46498e70d9bf3"
},
{
"fixed": "67f16bf2cc1698fd50e01ee8a2becc5a8e6d3a3e"
},
{
"fixed": "77d210e8db4d61d43b2d16df66b1ec46fad2ee01"
},
{
"fixed": "9a9ab0d963621d9d12199df9817e66982582d5a5"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-52609.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "2.6.29"
},
{
"fixed": "4.19.306"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.20.0"
},
{
"fixed": "5.4.268"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.209"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.148"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.75"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.14"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.7.2"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-52609.json"
}
}
],
"modified": "2026-10-28T02:30:47.869323790Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/252a2a5569eb9f8d16428872cc24dea1ac0bb097",
"https://git.kernel.org/stable/c/6696f76c32ff67fec26823fc2df46498e70d9bf3",
"https://git.kernel.org/stable/c/67f16bf2cc1698fd50e01ee8a2becc5a8e6d3a3e",
"https://git.kernel.org/stable/c/77d210e8db4d61d43b2d16df66b1ec46fad2ee01",
"https://git.kernel.org/stable/c/7e7a0d86542b0ea903006d3f42f33c4f7ead6918",
"https://git.kernel.org/stable/c/95b1d336b0642198b56836b89908d07b9a0c9608",
"https://git.kernel.org/stable/c/98fee5bee97ad47b527a997d5786410430d1f0e9",
"https://git.kernel.org/stable/c/9a9ab0d963621d9d12199df9817e66982582d5a5",
"https://lists.debian.org/debian-lts-announce/2024/06/msg00016.html",
"https://lists.debian.org/debian-lts-announce/2024/06/msg00020.html",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/52xxx/CVE-2023-52609.json",
"https://nvd.nist.gov/vuln/detail/CVE-2023-52609",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/52xxx/CVE-2023-52609.json"
}
},
"related_cves": [
{
"value": "CVE-2023-52609",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 515838,
"published_at": "2024-03-18T10:07:45.486+00:00"
}