Binder cleanup delay via mmput exit race
Published Mar 18, 2024 · Updated May 11, 2026
Race condition in the Binder driver in Linux allows local users to delay Binder cleanup and associated death notifications. binder_update_page_range() can retain a remote memory map across do_exit(), causing its final mmput() to queue cleanup on a task that sleeps awaiting the exited peer. The race requires low-privileged local access and concurrent Binder activity; cleanup remains blocked until another Binder event returns the task to user space.
Summary
What happened
Race condition in the Binder driver in Linux allows local users to delay Binder cleanup and associated death notifications. binder_update_page_range() can retain a remote memory map across do_exit(), causing its final mmput() to queue cleanup on a task that sleeps awaiting the exited peer. The race requires low-privileged local access and concurrent Binder activity; cleanup remains blocked until another Binder event returns the task to user space.
The record
- CVE
- CVE-2023-52609
- Published
- Mar 18, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-362, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 18, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.29
- Affected versionversion=457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 <252a2a5569eb9f8d16428872cc24dea1ac0bb097
- Affected versionversion=457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 <6696f76c32ff67fec26823fc2df46498e70d9bf3
- Affected versionversion=457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 <67f16bf2cc1698fd50e01ee8a2becc5a8e6d3a3e
- Affected versionversion=457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 <77d210e8db4d61d43b2d16df66b1ec46fad2ee01
- Affected versionversion=457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 <7e7a0d86542b0ea903006d3f42f33c4f7ead6918
- Affected versionversion=457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 <95b1d336b0642198b56836b89908d07b9a0c9608
- Affected versionversion=457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 <98fee5bee97ad47b527a997d5786410430d1f0e9
- Affected versionversion=457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 <9a9ab0d963621d9d12199df9817e66982582d5a5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo