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-2025-39977futex: Prevent use-after-free during requeue-PI

Description

In the Linux kernel, the following vulnerability has been resolved: futex: Prevent use-after-free during requeue-PI syzbot managed to trigger the following race: T1 T2 futex_wait_requeue_pi() futex_do_wait() schedule() futex_requeue() futex_proxy_trylock_atomic() futex_requeue_pi_prepare() requeue_pi_wake_futex() futex_requeue_pi_complete() /* preempt */ * timeout/ signal wakes T1 * futex_requeue_pi_wakeup_sync() // Q_REQUEUE_PI_LOCKED futex_hash_put() // back to userland, on stack futex_q is garbage /* back */ wake_up_state(q->task, TASK_NORMAL); In this scenario futex_wait_requeue_pi() is able to leave without using futex_q::lock_ptr for synchronization. This can be prevented by reading futex_q::task before updating the futex_q::requeue_state. A reference on the task_struct is not needed because requeue_pi_wake_futex() is invoked with a spinlock_t held which implies a RCU read section. Even if T1 terminates immediately after, the task_struct will remain valid during T2's wake_up_state(). A READ_ONCE on futex_q::task before futex_requeue_pi_complete() is enough because it ensures that the variable is read before the state is updated. Read futex_q::task before updating the requeue state, use it for the following wakeup.

Timeline

  1. ID reserved

    By Linux

  2. · 6 months later

    Published

  3. · 13 months 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-2025-39977, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Deferred3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.15% · top 95% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 07d91ef510fb16a2e0ca7453222105835b7ba3b8 – < cb5d19a61274b51b49601214a87af573b43d60fa
    • affected 07d91ef510fb16a2e0ca7453222105835b7ba3b8 – < 348736955ed6ca6e99ca24b93b1d3fbfe352c181
    • affected 07d91ef510fb16a2e0ca7453222105835b7ba3b8 – < a170b9c0dde83312b8b58ccc91509c7c15711641
    • affected 07d91ef510fb16a2e0ca7453222105835b7ba3b8 – < d824b2dbdcfe3c390278dd9652ea526168ef6850
    • affected 07d91ef510fb16a2e0ca7453222105835b7ba3b8 – < b549113738e8c751b613118032a724b772aa83f2
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 6.1.155 – ≤ 6.1.*
    • unaffected 6.6.109 – ≤ 6.6.*
    • unaffected 6.12.50 – ≤ 6.12.*
    • unaffected 6.16.10 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .