CVSS 3.1
7.8 highCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HHigh (7.8) in linux linux. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExplain CVE-2025-39976 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-39976?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-39976?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-39976 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | 6.16 and later |
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.16 | 6.16.10 |
| Linux | later releases | 6.17 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 14 | linux | 6.16.10-1 | DEBIAN-CVE-2025-39976 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2025-39976 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2025-39976 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2025-39976 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 more | no fix listed | UBUNTU-CVE-2025-39976 |
| Ubuntu | 24.04:LTS | linux-riscv, linux-oem-6.8, linux-gcp-6.11 and 6 more | no fix listed | UBUNTU-CVE-2025-39976 |
| Ubuntu | 25.10 | linux | 6.17.0-6.6 | UBUNTU-CVE-2025-39976 |
| Ubuntu | 25.10 | linux-aws, linux-gcp, linux-oracle | 6.17.0-1003.3 | UBUNTU-CVE-2025-39976 |
| Ubuntu | 25.10 | linux-azure | 6.17.0-1006.6 | UBUNTU-CVE-2025-39976 |
| Ubuntu | 25.10 | linux-azure-fde | no fix listed | UBUNTU-CVE-2025-39976 |
| Ubuntu | 25.10 | linux-raspi | 6.17.0-1004.4 | UBUNTU-CVE-2025-39976 |
| Ubuntu | 25.10 | linux-realtime | 6.17.0-1002.3 | UBUNTU-CVE-2025-39976 |
| Ubuntu | 25.10 | linux-riscv | 6.17.0-6.6.1 | UBUNTU-CVE-2025-39976 |
| Alpaquita | stream | linux-lts | 6.18.35-r1 | BELL-CVE-2025-39976 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.
Red Hat rates this Moderate.
A moderate-impact flaw was found in the Linux kernel's futex subsystem. When copy_process() fails in its call to futex_hash_allocate_default(), it takes an incorrect error-exit path: control jumps to the bad_fork_core_free label, which releases tasklist_lock and siglock even though neither lock has been acquired at that point. If a local process hits this failure path during process creation, the kernel is left in an inconsistent locking state, which can lead to a deadlock or other kernel instability. Red Hat rates this flaw as Moderate (CVSS 4.5, local attack vector, high attack complexity, low privileges required) because the flawed path is only reached when an internal allocation fails during fork/clone, making it difficult to trigger reliably, with limited impact on confidentiality, integrity, and availability. This differs from the CVE.org severity of 7.8 (Important), which assumes low attack complexity and high confidentiality, integrity, and availability impact. The affected code was introduced upstream in Linux kernel 6.16 and is not present in the Red Hat Enterprise Linux 7, 8, 9, and 10 kernels (including kernel-rt) or in Red Hat In-Vehicle OS, so those products are not affected; the flaw is only recorded against Red Hat Enterprise Linux 6 Extended Lifecycle Support, which is out of support scope.
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Not affected | |
| Red Hat Enterprise Linux 6 | kernel | Out of support scope | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Not affected | |
| Red Hat Enterprise Linux 8 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 9 | kernel | Not affected | |
| Red Hat Enterprise Linux 9 | kernel-rt | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-39976.