Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-26606binder: signal epoll threads of self-work

Description

In the Linux kernel, the following vulnerability has been resolved: binder: signal epoll threads of self-work In (e)poll mode, threads often depend on I/O events to determine when data is ready for consumption. Within binder, a thread may initiate a command via BINDER_WRITE_READ without a read buffer and then make use of epoll_wait() or similar to consume any responses afterwards. It is then crucial that epoll threads are signaled via wakeup when they queue their own work. Otherwise, they risk waiting indefinitely for an event leaving their work unhandled. What is worse, subsequent commands won't trigger a wakeup either as the thread has pending work.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-26606, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.24% · top 84% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 – < dd64bb8329ce0ea27bc557e4160c2688835402ac
    • affected 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 – < 42beab162dcee1e691ee4934292d51581c29df61
    • affected 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 – < a423042052ec2bdbf1e552e621e6a768922363cc
    • affected 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 – < 82722b453dc2f967b172603e389ee7dc1b3137cc
    • affected 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 – < 90e09c016d72b91e76de25f71c7b93d94cc3c769
    • affected 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 – < a7ae586f6f6024f490b8546c8c84670f96bb9b68
    • affected 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 – < 93b372c39c40cbf179e56621e6bc48240943af69
    • affected 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 – < 97830f3c3088638ff90b20dfba2eb4d487bf14d7
  • Linux · Linux

    • affected 2.6.29
    • unaffected < 2.6.29
    • unaffected 4.19.307 – ≤ 4.19.*
    • unaffected 5.4.269 – ≤ 5.4.*
    • unaffected 5.10.210 – ≤ 5.10.*
    • unaffected 5.15.149 – ≤ 5.15.*
    • unaffected 6.1.79 – ≤ 6.1.*
    • unaffected 6.6.18 – ≤ 6.6.*
    • unaffected 6.7.6 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References

References11

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-26606 badge
[![CVE-2024-26606](https://cveledger.app/badge/CVE-2024-26606.svg)](https://cveledger.app/cve/CVE-2024-26606)

Record last updated .