Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-39977: futex: Prevent use-after-free during requeue-PI

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 348736955ed6ca6e99ca24b93b1d3fbfe352c181, a170b9c0dde83312b8b58ccc91509c7c15711641, b549113738e8c751b613118032a724b772aa83f2; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-1.

Low priority for now. Upgrade to Linux Linux 348736955ed6ca6e99ca24b93b1d3fbfe352c181, a170b9c0dde83312b8b58ccc91509c7c15711641, b549113738e8c751b613118032a724b772aa83f2; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Oct 15, 2025
Updated
Nov 10, 2026
EPSS
0.1% · 4th percentile
CWE
—

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-39977

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.15affected
    • 07d91ef510fb16a2e0ca7453222105835b7ba3b8 and later · before cb5d19a61274b51b49601214a87af573b43d60faaffected · git
    • 07d91ef510fb16a2e0ca7453222105835b7ba3b8 and later · before 348736955ed6ca6e99ca24b93b1d3fbfe352c181affected · git
    • 07d91ef510fb16a2e0ca7453222105835b7ba3b8 and later · before a170b9c0dde83312b8b58ccc91509c7c15711641affected · git
    • 07d91ef510fb16a2e0ca7453222105835b7ba3b8 and later · before d824b2dbdcfe3c390278dd9652ea526168ef6850affected · git
    • 07d91ef510fb16a2e0ca7453222105835b7ba3b8 and later · before b549113738e8c751b613118032a724b772aa83f2affected · git
    • before 5.15not affected · semver
    • 6.1.155 and later · up to and including 6.1.*not affected · semver
    • 6.6.109 and later · up to and including 6.6.*not affected · semver
    • 6.12.50 and later · up to and including 6.12.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.158-16.1.158-1
Debian:13linuxbefore 6.12.57-16.12.57-1
Debian:14linuxbefore 6.16.10-16.16.10-1
openSUSE:Leap 16.0dtb-aarch64before 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-64kbbefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-azurebefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-defaultbefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-default-basebefore 6.12.0-160000.9.1.160000.2.66.12.0-160000.9.1.160000.2.6
openSUSE:Leap 16.0kernel-docsbefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-kvmsmallbefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-obs-buildbefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-obs-qabefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-rtbefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-sourcebefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-symsbefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-zfcpdumpbefore 6.12.0-160000.9.16.12.0-160000.9.1
SUSE:Linux Enterprise Server 16.0kernel-azurebefore 6.12.0-160000.9.16.12.0-160000.9.1
SUSE:Linux Enterprise Server 16.0kernel-docsbefore 6.12.0-160000.9.16.12.0-160000.9.1
SUSE:Linux Enterprise Server 16.0kernel-kvmsmallbefore 6.12.0-160000.9.16.12.0-160000.9.1
SUSE:Linux Enterprise Server 16.0kernel-obs-qabefore 6.12.0-160000.9.16.12.0-160000.9.1
SUSE:Linux Enterprise Server 16.0kernel-symsbefore 6.12.0-160000.9.16.12.0-160000.9.1
SUSE:Linux Enterprise Server 16.0kernel-zfcpdumpbefore 6.12.0-160000.9.16.12.0-160000.9.1
SUSE:Linux Micro 6.2kernel-64kbbefore 6.12.0-160000.9.16.12.0-160000.9.1
SUSE:Linux Micro 6.2kernel-defaultbefore 6.12.0-160000.9.16.12.0-160000.9.1

+4

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-39975Oct 15, 2025 · smb: client: fix wrong index reference in smb2_compound_op()
    39Monitor
  • ← EarlierCVE-2025-39976Oct 15, 2025 · futex: Use correct exit on failure from futex_hash_allocate_default()
    31Monitor
  • Later →CVE-2025-39978Oct 15, 2025 · octeontx2-pf: Fix potential use after free in otx2_tc_add_flow()
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux348736955ed6ca6e99ca24b93b1d3fbfe352c181Vendor (CNA)
Linux Linuxa170b9c0dde83312b8b58ccc91509c7c15711641Vendor (CNA)
Linux Linuxb549113738e8c751b613118032a724b772aa83f2Vendor (CNA)
Linux Linuxcb5d19a61274b51b49601214a87af573b43d60faVendor (CNA)
Linux Linuxd824b2dbdcfe3c390278dd9652ea526168ef6850Vendor (CNA)
azl3 kernel 6.6.104.2-4 on Azure Linux 3.06.6.112.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.158-1 · Debian:12Package registry (OSV)
opensuse:dtb-aarch646.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-64kb6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-azure6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default-base6.12.0-160000.9.1.160000.2.6 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-docs6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-kvmsmall6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-build6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-qa6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-rt6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-source6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-syms6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
suse:kernel-64kb6.12.0-160000.9.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-azure6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-default6.12.0-160000.9.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-default-base6.12.0-160000.9.1.160000.2.6 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-docs6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-kvmsmall6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-obs-build6.12.0-160000.9.1 · SUSE:Linux Micro Extras 6.2Package registry (OSV)
suse:kernel-obs-qa6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-rt6.12.0-160000.9.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-source6.12.0-160000.9.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-syms6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)

+1

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records