Bug 2404095 (CVE-2025-39976) - CVE-2025-39976 kernel: futex: Use correct exit on failure from futex_hash_allocate_default()
Summary: CVE-2025-39976 kernel: futex: Use correct exit on failure from futex_hash_all...
Keywords:
Status: NEW
Alias: CVE-2025-39976
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-10-15 08:01 UTC by OSIDB Bzimport
Modified: 2025-10-16 12:24 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-10-15 08:01:36 UTC
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().


Note You need to log in before you can comment on or make changes to this bug.