cgroup: Add missing cpus_read_lock() to cgroup_attach_task_all()
Noroxi assessment
Priority: Monitor (action score 22/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.17% (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 07191f984842d50020789ff14c75da436a7f46a9, 321488cfac7d0eb6d97de467015ff754f85813ff, 43626dade36fa74d3329046f4ae2d7fdefe401c6.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 07191f984842d50020789ff14c75da436a7f46a9, 321488cfac7d0eb6d97de467015ff754f85813ff, 43626dade36fa74d3329046f4ae2d7fdefe401c6 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: cgroup: Add missing cpus_read_lock() to cgroup_attach_task_all() syzbot is hitting percpu_rwsem_assert_held(&cpu_hotplug_lock) warning at cpuset_attach() [1], for commit 4f7e7236435ca0ab ("cgroup: Fix threadgroup_rwsem <-> cpus_read_lock() deadlock") missed that cpuset_attach() is also called from cgroup_attach_task_all(). Add cpus_read_lock() like what cgroup_procs_write_start() does.
- Published
- May 3, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-667
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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 kernel5.4.213 and later · before 5.4.215
- linux linux kernel5.10.143 and later · before 5.10.145
- linux linux kernelafter 5.15.68 · before 5.15.70
- linux linux kernel5.19.9 and later · before 5.19.11
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
- e446300968c6bd25d9cd6c33b9600780a39b3975 and later · before 321488cfac7d0eb6d97de467015ff754f85813ffaffected · git
- 59c6902a96b4439e07c25ef86a4593bea5481c3b and later · before 07191f984842d50020789ff14c75da436a7f46a9affected · git
- dee1e2b18cf5426eed985512ccc6636ec69dbdd6 and later · before 9f267393b036f1470fb12fb892d59e7ff8aeb58daffected · git
- 3bf4bf54069f9b62a54988e5d085023c17a66c90 and later · before 5db17805b6ba4c34dab303f49aea3562fc25af75affected · git
- c0deb027c99c099aa6b831e326bfba802b25e774 and later · before 99bc25748e394d17f9e8b10cc7f273b8e64c1c7eaffected · git
- 4f7e7236435ca0abe005c674ebd6892c6e83aeb3 and later · before 43626dade36fa74d3329046f4ae2d7fdefe401c6affected · git
- 5.4.213 and later · before 5.4.215affected · semver
- 5.10.143 and later · before 5.10.145affected · semver
- 5.15.68 and later · before 5.15.70affected · semver
- 5.19.9 and later · before 5.19.11affected · semver
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 5.19.11-1 | 5.19.11-1 |
| SUSE:Linux Enterprise Micro 5.3 | kernel-rt | before 5.14.21-150400.15.106.1 | 5.14.21-150400.15.106.1 |
| SUSE:Linux Enterprise Micro 5.3 | kernel-source-rt | before 5.14.21-150400.15.106.1 | 5.14.21-150400.15.106.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-2024-27078May 1, 2024 · media: v4l2-tpg: fix some memleaks in tpg_alloc22Monitor
- ← EarlierCVE-2022-48670May 3, 2024 · peci: cpu: Fix use-after-free in adev_release()31Monitor
- Later →CVE-2022-48672May 3, 2024 · of: fdt: fix off-by-one error in unflatten_dt_nodes()31Monitor
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 | 07191f984842d50020789ff14c75da436a7f46a9 | Vendor (CNA) |
| Linux Linux | 321488cfac7d0eb6d97de467015ff754f85813ff | Vendor (CNA) |
| Linux Linux | 43626dade36fa74d3329046f4ae2d7fdefe401c6 | Vendor (CNA) |
| Linux Linux | 5.10.145 | Vendor (CNA) |
| Linux Linux | 5.15.70 | Vendor (CNA) |
| Linux Linux | 5.19.11 | Vendor (CNA) |
| Linux Linux | 5.4.215 | Vendor (CNA) |
| Linux Linux | 5db17805b6ba4c34dab303f49aea3562fc25af75 | Vendor (CNA) |
| Linux Linux | 99bc25748e394d17f9e8b10cc7f273b8e64c1c7e | Vendor (CNA) |
| Linux Linux | 9f267393b036f1470fb12fb892d59e7ff8aeb58d | Vendor (CNA) |
| debian:linux | 5.19.11-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-rt | 5.14.21-150400.15.106.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:kernel-source-rt | 5.14.21-150400.15.106.1 · SUSE:Linux Enterprise Micro 5.3 | 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0494 · May 16, 2024(Linux Kernel Güncellemesi)
- TR-24-0432 · May 6, 2024(Linux Kernel Güncellemesi)
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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-667 · Improper LockingCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/321488cfac7d0eb6d97de467015ff754f85813ff
- git.kernel.org/stable/c/43626dade36fa74d3329046f4ae2d7fdefe401c6
- git.kernel.org/stable/c/5db17805b6ba4c34dab303f49aea3562fc25af75
- git.kernel.org/stable/c/99bc25748e394d17f9e8b10cc7f273b8e64c1c7e
- git.kernel.org/stable/c/9f267393b036f1470fb12fb892d59e7ff8aeb58d
Vendor advisories and official records. Exploit/PoC links are deliberately left out.