Local Binder thread hang via missed self-wakeup
Published Feb 26, 2024 · Updated May 11, 2026
Denial of service in the Linux Binder driver allows local users to hang Binder threads by queuing work for their own thread. In drivers/android/binder.c, binder_poll() fails to wake an epoll thread when its BINDER_WRITE_READ request queues self-work without a read buffer. Local Binder-device access and a polling workflow are required; the thread can wait indefinitely with queued work unhandled, and later commands do not wake it.
Summary
What happened
Denial of service in the Linux Binder driver allows local users to hang Binder threads by queuing work for their own thread. In drivers/android/binder.c, binder_poll() fails to wake an epoll thread when its BINDER_WRITE_READ request queues self-work without a read buffer. Local Binder-device access and a polling workflow are required; the thread can wait indefinitely with queued work unhandled, and later commands do not wake it.
The record
- CVE
- CVE-2024-26606
- Published
- Feb 26, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 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 <42beab162dcee1e691ee4934292d51581c29df61
- Affected versionversion=457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 <82722b453dc2f967b172603e389ee7dc1b3137cc
- Affected versionversion=457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 <90e09c016d72b91e76de25f71c7b93d94cc3c769
- Affected versionversion=457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 <93b372c39c40cbf179e56621e6bc48240943af69
- Affected versionversion=457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 <97830f3c3088638ff90b20dfba2eb4d487bf14d7
- Affected versionversion=457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 <a423042052ec2bdbf1e552e621e6a768922363cc
- Affected versionversion=457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 <a7ae586f6f6024f490b8546c8c84670f96bb9b68
- Affected versionversion=457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 <dd64bb8329ce0ea27bc557e4160c2688835402ac
What conditions does exploitation require?
What is affected?
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
No sourced classifications are available.
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