locking/ww_mutex/test: Fix potential workqueue corruption
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 304a2c4aad0fff887ce493e4197bf9cbaf394479, 9ed2d68b3925145f5f51c46559484881d6082f75, bccdd808902f8c677317cec47c306e42b93b849e.
Low priority for now. Upgrade to Linux Linux 304a2c4aad0fff887ce493e4197bf9cbaf394479, 9ed2d68b3925145f5f51c46559484881d6082f75, bccdd808902f8c677317cec47c306e42b93b849e or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 21, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-787
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 4.14.331
- linux linux kernel4.15 and later · before 4.19.300
- linux linux kernel4.20 and later · before 5.4.262
- linux linux kernel5.5 and later · before 5.10.202
- linux linux kernel5.11 and later · before 5.15.140
- linux linux kernel5.16 and later · before 6.1.64
- linux linux kernel6.2 and later · before 6.5.13
- linux linux kernel6.6 and later · before 6.6.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.11affected
- 2a0c11282881875dc44f166a20eedf0d866dd0ef and later · before d4d37c9e6a4dbcca958dabd99216550525c7e389affected · git
- 2a0c11282881875dc44f166a20eedf0d866dd0ef and later · before d8267cabbe1bed15ccf8b0e684c528bf8eeef715affected · git
- 2a0c11282881875dc44f166a20eedf0d866dd0ef and later · before dcd85e3c929368076a7592b27f541e0da8b427f5affected · git
- 2a0c11282881875dc44f166a20eedf0d866dd0ef and later · before 9ed2d68b3925145f5f51c46559484881d6082f75affected · git
- 2a0c11282881875dc44f166a20eedf0d866dd0ef and later · before e89d0ed45a419c485bae999426ecf92697cbdda3affected · git
- 2a0c11282881875dc44f166a20eedf0d866dd0ef and later · before c56df79d68677cf062da1b6e3b33e74299a92dfcaffected · git
- 2a0c11282881875dc44f166a20eedf0d866dd0ef and later · before e36407713163363e65566e7af0abe207d5f59a0caffected · git
- 2a0c11282881875dc44f166a20eedf0d866dd0ef and later · before 304a2c4aad0fff887ce493e4197bf9cbaf394479affected · git
- 2a0c11282881875dc44f166a20eedf0d866dd0ef and later · before bccdd808902f8c677317cec47c306e42b93b849eaffected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.64-1 | 6.1.64-1 |
| Debian:13 | linux | before 6.6.8-1 | 6.6.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
Published before and after this one in the same product
- ← EarlierCVE-2023-52834May 21, 2024 · atl1c: Work around the DMA RX overflow issue22Monitor
- ← EarlierCVE-2023-52835May 21, 2024 · perf/core: Bail out early if the request AUX area is out of bound31Monitor
- Later →CVE-2023-52837May 21, 2024 · nbd: fix uaf in nbd_open31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 304a2c4aad0fff887ce493e4197bf9cbaf394479 | Vendor (CNA) |
| Linux Linux | 9ed2d68b3925145f5f51c46559484881d6082f75 | Vendor (CNA) |
| Linux Linux | bccdd808902f8c677317cec47c306e42b93b849e | Vendor (CNA) |
| Linux Linux | c56df79d68677cf062da1b6e3b33e74299a92dfc | Vendor (CNA) |
| Linux Linux | d4d37c9e6a4dbcca958dabd99216550525c7e389 | Vendor (CNA) |
| Linux Linux | d8267cabbe1bed15ccf8b0e684c528bf8eeef715 | Vendor (CNA) |
| Linux Linux | dcd85e3c929368076a7592b27f541e0da8b427f5 | Vendor (CNA) |
| Linux Linux | e36407713163363e65566e7af0abe207d5f59a0c | Vendor (CNA) |
| Linux Linux | e89d0ed45a419c485bae999426ecf92697cbdda3 | Vendor (CNA) |
| debian:linux | 6.1.64-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/9ed2d68b3925145f5f51c46559484881d6082f75
- git.kernel.org/stable/c/bccdd808902f8c677317cec47c306e42b93b849e
- git.kernel.org/stable/c/c56df79d68677cf062da1b6e3b33e74299a92dfc
- git.kernel.org/stable/c/d4d37c9e6a4dbcca958dabd99216550525c7e389
- git.kernel.org/stable/c/d8267cabbe1bed15ccf8b0e684c528bf8eeef715
- git.kernel.org/stable/c/dcd85e3c929368076a7592b27f541e0da8b427f5
- git.kernel.org/stable/c/e36407713163363e65566e7af0abe207d5f59a0c
- git.kernel.org/stable/c/e89d0ed45a419c485bae999426ecf92697cbdda3
Vendor advisories and official records. Exploit/PoC links are deliberately left out.