locking/ww_mutex/test: Fix potential workqueue corruption
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 304a2c4aad0fff887ce493e4197bf9cbaf394479, Kernel 9ed2d68b3925145f5f51c46559484881d6082f75, Kernel bccdd808902f8c677317cec47c306e42b93b849e and 6 more.
In the Linux kernel, the following vulnerability has been resolved: locking/ww_mutex/test: Fix potential workqueue corruption In some cases running with the test-ww_mutex code, I was seeing odd behavior where sometimes it seemed flush_workqueue was returning before all the work threads were finished. Often this would cause strange crashes as the mutexes would be freed while they were being used. Looking at the code, there is a lifetime problem as the controlling thread that spawns the work allocates the "struct stress" structures that are passed to the workqueue threads. Then when the workqueue threads are finished, they free the stress struct that was passed to them. Unfortunately the workqueue work_struct node is in the stress struct. Which means the work_struct is freed before the work thread returns and while flush_workqueue is waiting. It seems like a better idea to have the controlling thread both allocate and free the stress structures, so that we can be sure we don't corrupt the workqueue by freeing the structure prematurely. So this patch reworks the test to do so, and with this change I no longer see the early flush_workqueue returns.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =4.11, >=2a0c11282881875dc44f166a20eedf0d866dd0ef <304a2c4aad0fff887ce493e4197bf9cbaf394479, >=2a0c11282881875dc44f166a20eedf0d866dd0ef <9ed2d68b3925145f5f51c46559484881d6082f75, >=2a0c11282881875dc44f166a20eedf0d866dd0ef <bccdd808902f8c677317cec47c306e42b93b849e, >=2a0c11282881875dc44f166a20eedf0d866dd0ef <c56df79d68677cf062da1b6e3b33e74299a92dfc, >=2a0c11282881875dc44f166a20eedf0d866dd0ef <d4d37c9e6a4dbcca958dabd99216550525c7e389, >=2a0c11282881875dc44f166a20eedf0d866dd0ef <d8267cabbe1bed15ccf8b0e684c528bf8eeef715, >=2a0c11282881875dc44f166a20eedf0d866dd0ef <dcd85e3c929368076a7592b27f541e0da8b427f5, >=2a0c11282881875dc44f166a20eedf0d866dd0ef <e36407713163363e65566e7af0abe207d5f59a0c, >=2a0c11282881875dc44f166a20eedf0d866dd0ef <e89d0ed45a419c485bae999426ecf92697cbdda3 | 304a2c4aad0fff887ce493e4197bf9cbaf394479, 9ed2d68b3925145f5f51c46559484881d6082f75, bccdd808902f8c677317cec47c306e42b93b849e, c56df79d68677cf062da1b6e3b33e74299a92dfc, d4d37c9e6a4dbcca958dabd99216550525c7e389, d8267cabbe1bed15ccf8b0e684c528bf8eeef715, dcd85e3c929368076a7592b27f541e0da8b427f5, e36407713163363e65566e7af0abe207d5f59a0c, e89d0ed45a419c485bae999426ecf92697cbdda3 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket