CVE-2025-39976

High

In the Linux kernel, the following vulnerability has been resolved: futex: Use correct exit on failure from futex_hash_allocate_default() copy_process() uses the wrong error exit path from futex_hash_allocate_default(). After exiting from futex_hash_allocate_default(), neither tasklist_lock nor siglock has been acquired. The exit label bad_fork_core_free unlocks both of these locks which is wrong. The next exit label, bad_fork_cancel_cgroup, is the correct exit. sched_cgroup_fork() did not allocate any resources that need to freed. Use bad_fork_cancel_cgroup on error exit from futex_hash_allocate_default().

Package Linux Kernel
Published 2025-10-15
Last modified 2026-07-30
CVSS version 3.1
Patch available
Yes

CVSS 3.1 score

7.8

out of 10
High
Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected versions

Linux kernel versions 6.16 and later are affected. Fixed in 6.16.10, 6.17 and their respective stable series.

Affected from
≥ 6.16
Fixed in
✓ 6.16.10 6.16.x ✓ 6.17

Frequently asked questions

  • What is CVE-2025-39976?

    CVE-2025-39976 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10 . It affects Linux kernel versions from 6.16 onward and has been patched in 6.16.10 and 6.17. CVE-2025-39976 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

  • What is the CVSS score for CVE-2025-39976?

    CVE-2025-39976 has a CVSS score of 7.8 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H .

  • Is there a patch available for CVE-2025-39976?

    Yes. CVE-2025-39976 has been patched. Fixed versions include 6.16.10 and 6.17. If you are running Linux kernel 6.16 or later up to the fix versions, apply the relevant patch for your kernel branch.

  • Is CVE-2025-39976 actively exploited?

    No. CVE-2025-39976 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.