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-2026-80920io_uring: defer eventfd signaling when queued from a wakeup handler

Description

In the Linux kernel, the following vulnerability has been resolved: io_uring: defer eventfd signaling when queued from a wakeup handler io_req_local_work_add() signals the CQ ring eventfd inline when it is the one to push the first entry onto ->work_list. For DEFER_TASKRUN rings that add is frequently done from a waitqueue wakeup handler, where an arbitrary waitqueue lock is held. eventfd_signal_mask() only refuses to recurse when current->in_eventfd is set, but that bit is set by eventfd_signal_mask() itself. If the wake chain starts somewhere else, signal goes out inline and can feed back into epoll. Add IOU_F_TWQ_IN_WAKE, set it on the task_work add done from the three waitqueue callbacks, and use it to force io_eventfd_signal() down the existing call_rcu_hurry() deferral instead of signaling inline.

Timeline

  1. ID reserved

    By Linux

  2. · 14 days later

    Published

  3. · 42 days 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (14 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 21a091b970cdbcf3e8ff829234b51be6f9192766 – < d0c240f25e654442a72af5ca021a02165ccce638
    • affected 21a091b970cdbcf3e8ff829234b51be6f9192766 – < 9d984451baf768ecd9e1fdad4637b729fcb2c9d5
    • affected 21a091b970cdbcf3e8ff829234b51be6f9192766 – < e22f4494cc9487d326e5e3067f33dea7c1e442b2
    • affected 21a091b970cdbcf3e8ff829234b51be6f9192766 – < b6bb334b0e9348887e3e55e1f494b0c3b8fbf59f
    • affected 21a091b970cdbcf3e8ff829234b51be6f9192766 – < 40b6ccf68731809ceb85c6e9f0f8f2ed61c7aa5a
    • affected 21a091b970cdbcf3e8ff829234b51be6f9192766 – < cd305ee3633a45fcf5f3a5d83f99f3cb77d87b6e
  • Linux · Linux

    • affected 6.1
    • unaffected < 6.1
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.49 – ≤ 6.18.*
    • unaffected 7.1.11 – ≤ 7.1.*
    • unaffected 7.2.1 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .