Description
In the Linux kernel, the following vulnerability has been resolved: PCI/DOE: Fix destroy_work_on_stack() race The following debug object splat was observed in testing: ODEBUG: free active (active state 0) object: 0000000097d23782 object type: work_struct hint: doe_statemachine_work+0x0/0x510 WARNING: CPU: 1 PID: 71 at lib/debugobjects.c:514 debug_print_object+0x7d/0xb0 ... Workqueue: pci 0000:36:00.0 DOE [1 doe_statemachine_work RIP: 0010:debug_print_object+0x7d/0xb0 ... Call Trace: ? debug_print_object+0x7d/0xb0 ? __pfx_doe_statemachine_work+0x10/0x10 debug_object_free.part.0+0x11b/0x150 doe_statemachine_work+0x45e/0x510 process_one_work+0x1d4/0x3c0 This occurs because destroy_work_on_stack() was called after signaling the completion in the calling thread. This creates a race between destroy_work_on_stack() and the task->work struct going out of scope in pci_doe(). Signal the work complete after destroying the work struct. This is safe because signal_task_complete() is the final thing the work item does and the workqueue code is careful not to access the work struct after.
Product status
2a0e0f4773fe8032fb17e56f897bee32ce3cdc2b (git) before d96799ee3b78962c80e4b6653734f488f999ca09
abf04be0e7071f2bcd39bf97ba407e7d4439785e (git) before c4f9c0a3a6df143f2e1092823b7fa9e07d6ab57f
abf04be0e7071f2bcd39bf97ba407e7d4439785e (git) before 19cf3ba16dcc2ef059dcf010072d4f96d76486e0
abf04be0e7071f2bcd39bf97ba407e7d4439785e (git) before e3a3a097eaebaf234a482b4d2f9f18fe989208c1
95628b830952943631d3d74f73f431f501c5d6f5 (git)
6.3
Any version before 6.3
6.1.53 (semver)
6.4.16 (semver)
6.5.3 (semver)
6.6 (original_commit_for_fix)
References
git.kernel.org/...c/d96799ee3b78962c80e4b6653734f488f999ca09
git.kernel.org/...c/c4f9c0a3a6df143f2e1092823b7fa9e07d6ab57f
git.kernel.org/...c/19cf3ba16dcc2ef059dcf010072d4f96d76486e0
git.kernel.org/...c/e3a3a097eaebaf234a482b4d2f9f18fe989208c1
Data based on CVE®. Copyright © 1999-2025, The MITRE Corporation. All rights reserved.
