Bug 2348587 (CVE-2025-21786) - CVE-2025-21786 kernel: workqueue: Put the pwq after detaching the rescuer from the pool
Summary: CVE-2025-21786 kernel: workqueue: Put the pwq after detaching the rescuer fro...
Keywords:
Status: NEW
Alias: CVE-2025-21786
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-02-27 03:04 UTC by OSIDB Bzimport
Modified: 2025-11-11 10:25 UTC (History)
4 users (show)

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


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2025:20095 0 None None None 2025-11-11 08:02:24 UTC
Red Hat Product Errata RHSA-2025:20518 0 None None None 2025-11-11 10:25:47 UTC

Description OSIDB Bzimport 2025-02-27 03:04:13 UTC
In the Linux kernel, the following vulnerability has been resolved:

workqueue: Put the pwq after detaching the rescuer from the pool

The commit 68f83057b913("workqueue: Reap workers via kthread_stop() and
remove detach_completion") adds code to reap the normal workers but
mistakenly does not handle the rescuer and also removes the code waiting
for the rescuer in put_unbound_pool(), which caused a use-after-free bug
reported by Cheung Wall.

To avoid the use-after-free bug, the pool’s reference must be held until
the detachment is complete. Therefore, move the code that puts the pwq
after detaching the rescuer from the pool.

Comment 2 errata-xmlrpc 2025-11-11 08:02:22 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2025:20095 https://access.redhat.com/errata/RHSA-2025:20095

Comment 3 errata-xmlrpc 2025-11-11 10:25:46 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2025:20518 https://access.redhat.com/errata/RHSA-2025:20518


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