CVE-2023-52836
Linux Kernel Workqueue Corruption in WW Mutex Test
Description
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.
INFO
Published Date :
May 21, 2024, 4:15 p.m.
Last Modified :
May 21, 2024, 4:53 p.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
Exploitability Score :
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2023-52836
.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2023-52836
vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2023-52836
vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 29, 2024
Action Type Old Value New Value -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 21, 2024
Action Type Old Value New Value Added Description 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. Added Reference kernel.org https://git.kernel.org/stable/c/d4d37c9e6a4dbcca958dabd99216550525c7e389 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/d8267cabbe1bed15ccf8b0e684c528bf8eeef715 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/dcd85e3c929368076a7592b27f541e0da8b427f5 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/9ed2d68b3925145f5f51c46559484881d6082f75 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/e89d0ed45a419c485bae999426ecf92697cbdda3 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/c56df79d68677cf062da1b6e3b33e74299a92dfc [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/e36407713163363e65566e7af0abe207d5f59a0c [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/304a2c4aad0fff887ce493e4197bf9cbaf394479 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/bccdd808902f8c677317cec47c306e42b93b849e [No types assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2023-52836
is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2023-52836
weaknesses.