CVE-2025-39976
published 2025-10-15CVE-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…
PriorityP335high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.13%
3.3th percentile
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
7 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.16.10-1 (forky) | linux 6.16.10-1 (forky) |
| linux | linux | — | — |
| linux | linux | >= 7c4f75a21f636486d2969d9b6680403ea8483539 < f1635765cd0fdbf27b04d9a50be91a01b5adda13 | f1635765cd0fdbf27b04d9a50be91a01b5adda13 |
| linux | linux | >= 7c4f75a21f636486d2969d9b6680403ea8483539 < 4ec3c15462b9f44562f45723a92e2807746ba7d1 | 4ec3c15462b9f44562f45723a92e2807746ba7d1 |
| linux | linux_kernel | >= 0 < 6.16.10-1 | 6.16.10-1 |
| linux | linux_kernel | >= 6.16.0 < 6.16.10 | 6.16.10 |
| msrc | azl3_libqb_2.0.8-1_on_azure_linux_3.0 | — | — |
CVSS provenance
nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vendor_msrc9.8CRITICAL
vendor_redhat4.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
futex: Use correct exit on failure from futex_hash_allocate_default()
osv·2025-10-15
CVE-2025-39976 futex: Use correct exit on failure from futex_hash_allocate_default()
futex: Use correct exit on failure from futex_hash_allocate_default()
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().
GHSA
GHSA-rgc5-qvp4-69x6: In the Linux kernel, the following vulnerability has been resolved:
futex: Use correct exit on failure from futex_hash_allocate_default()
copy_proce
ghsa_unreviewed·2025-10-15
CVE-2025-39976 GHSA-rgc5-qvp4-69x6: In the Linux kernel, the following vulnerability has been resolved:
futex: Use correct exit on failure from futex_hash_allocate_default()
copy_proce
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().
OSV
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
osv·2025-10-15
CVE-2025-39976 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
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().
Red Hat
kernel: futex: Use correct exit on failure from futex_hash_allocate_default()
vendor_redhat·2025-10-15·CVSS 4.5
CVE-2025-39976 [MEDIUM] CWE-703 kernel: futex: Use correct exit on failure from futex_hash_allocate_default()
kernel: futex: Use correct exit on failure from futex_hash_allocate_default()
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().
A flaw was found in the Linux kernel’s futex subsystem: when copy_process() fails in the call to futex_ha
Debian
CVE-2025-39976: linux - In the Linux kernel, the following vulnerability has been resolved: futex: Use ...
vendor_debian·2025
CVE-2025-39976 [LOW] CVE-2025-39976: linux - In the Linux kernel, the following vulnerability has been resolved: futex: Use ...
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().
Scope: local
bookworm: resolved
bullseye: resolved
forky: resolved (fixed in 6.16.10-1)
sid: resolved (fixed in 6.16.10-1)
trixie: resolved
Microsoft
log_blackbox.c in libqb before 2.0.8 allows a buffer overflow via long log messages because the header size is not considered.
vendor_msrc·2023-08-08·CVSS 9.8
CVE-2023-39976 [CRITICAL] CWE-120 log_blackbox.c in libqb before 2.0.8 allows a buffer overflow via long log messages because the header size is not considered.
log_blackbox.c in libqb before 2.0.8 allows a buffer overflow via long log messages because the header size is not considered.
FAQ: Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?
One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information. If impact to additional products is identified, we will update the CVE to reflect this.
Mariner: Mariner
mitre: mitre
Customer Action Req
No detection rules found.
No public exploits indexed.
2025-10-15
Published