CVE-2025-39976
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().
Affected versions
Linux kernel versions
6.16
and later are affected. Fixed in
6.16.10,
6.17
and their respective stable series.
References
The following references provide additional information about CVE-2025-39976 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.
-
PatchKernel patch commithttps://git.kernel.org/stable/c/4ec3c15462b9f44562f45723a92e2807746ba7d1
-
PatchKernel patch commithttps://git.kernel.org/stable/c/f1635765cd0fdbf27b04d9a50be91a01b5adda13
Frequently asked questions
-
What is CVE-2025-39976?
CVE-2025-39976 is a unscored severity Linux kernel vulnerability . 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.
-
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.