CVE-2023-52836

locking/ww_mutex/test: Fix potential workqueue corruption

HIGH
7.8
CVSS Score
Published: May 21, 2024 at 03:31 PM UTC
Updated: June 17, 2026 at 06:43 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 4.14.3314.11 ≤ v < 4.14.3314.11 ≤ v < 4.19.3004.11 ≤ v < 5.10.2024.11 ≤ v < 5.15.1404.11 ≤ v < 5.4.2624.11 ≤ v < 6.1.644.11 ≤ v < 6.5.134.11 ≤ v < 6.6.34.11 ≤ v < 6.74.15 ≤ v < 4.19.3004.20 ≤ v < 5.4.2625.11 ≤ v < 5.15.1405.16 ≤ v < 6.1.645.5 ≤ v < 5.10.2026.2 ≤ v < 6.5.136.6 ≤ v < 6.6.32a0c11282881875dc44f166a20eedf0d866dd0ef4.11
Vendor states this is fixed in 304a2c4aad0fff887ce493e4197bf9cbaf394479 (fixed)
Vendor states this is fixed in 9ed2d68b3925145f5f51c46559484881d6082f75 (fixed)
Vendor states this is fixed in bccdd808902f8c677317cec47c306e42b93b849e (fixed)
Vendor states this is fixed in c56df79d68677cf062da1b6e3b33e74299a92dfc (fixed)
Vendor states this is fixed in d4d37c9e6a4dbcca958dabd99216550525c7e389 (fixed)
Vendor states this is fixed in d8267cabbe1bed15ccf8b0e684c528bf8eeef715 (fixed)
Vendor states this is fixed in dcd85e3c929368076a7592b27f541e0da8b427f5 (fixed)
Vendor states this is fixed in e36407713163363e65566e7af0abe207d5f59a0c (fixed)
Vendor states this is fixed in e89d0ed45a419c485bae999426ecf92697cbdda3 (fixed)
Vendor states this is fixed in 4.11 (unaffected)
Vendor states this is fixed in 4.14.331 (unaffected)
Vendor states this is fixed in 4.19.300 (unaffected)
Vendor states this is fixed in 5.10.202 (unaffected)
Vendor states this is fixed in 5.15.140 (unaffected)
Vendor states this is fixed in 5.4.262 (unaffected)
Vendor states this is fixed in 6.1.64 (unaffected)
Vendor states this is fixed in 6.5.13 (unaffected)
Vendor states this is fixed in 6.6.3 (unaffected)
Vendor states this is fixed in 6.7 (unaffected)

References (9)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/304a2c4aad0fff887ce493e4197bf9cbaf394479
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/9ed2d68b3925145f5f51c46559484881d6082f75
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/bccdd808902f8c677317cec47c306e42b93b849e
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/c56df79d68677cf062da1b6e3b33e74299a92dfc
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/d4d37c9e6a4dbcca958dabd99216550525c7e389
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/d8267cabbe1bed15ccf8b0e684c528bf8eeef715
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/dcd85e3c929368076a7592b27f541e0da8b427f5
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/e36407713163363e65566e7af0abe207d5f59a0c

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card