CVE-2022-48671: cgroup: Add missing cpus_read_lock() to cgroup_attach_task_all()

Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available

What, why and how

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.

What

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

How

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: local access → Improper Locking → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface: Local
Privileges required: Low: a basic authenticated account is required
User interaction: None
Attack complexity: Low: no specialised conditions are recorded
Security boundary: Unchanged: impact remains within the vulnerable component's security authority
Weakness ? CWE means Common Weakness Enumeration: a standard category for the underlying weakness.: CWE-667 ↗
CWE-667: Improper Locking. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land: The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.

CWE-667

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2022-51366Official EUVD mapping

0 linked advisory records.

Official EUVD record

BSI · German · WID-SEC-W-2024-1025Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder um einen nicht spezifizierten Angriff durchzuführen.

Official advisory

CERT-FR · French · CERTFR-2025-AVI-0088Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2021-47517 Référence CVE CVE-2021-47598 https://www.cve.org/CVERecord?id=CVE-2021-47598 Référence CVE CVE-2022-36280 https://www.cve.org/CVERecord?id=CVE-2022-36280 Référence CVE CVE-2022-48632 https://www.cve.org/CVERecord?id=CVE-2022-48632 Référence CVE CVE-2022-48634 https://www.cve.org/CVERecord?id=CVE-2022-48634 Référence CVE CVE-2022-48636 https://www.cve.org/CVERecord?id=CVE-2022-48636 Référence CVE CVE-2022-48651 https://www.cve.org/CVERecord?id=CVE-2022-48651 Référence CVE CVE-2022-48652 https://www.cve.org/CVERecord?id=CVE-2022-48652 Référence CVE CVE-2022-48662 https://www.cve.org/CVERecord?id=CVE-2022-48662 Référence CVE CVE-2022-48671 https://www.cve.org/CVERecord?id=CVE-2022-48671 Référence CVE CVE-2022-48672 https://www.cve.org/CVERecord?id=CVE-2022-48672 Référence CVE CVE-2022-48673 https://www.cve.org/CVERecord?id=CVE-2022-48673 Référence CVE CVE-2022-48675 https://www.cve.org/CVERecord?id=CVE-2022-48675 Référence CVE CVE-2022-48686 https://www.cve.org/CVERecord?id=CVE-2022-48686 Référence CVE CVE-2022-48687 https://www.cve.org/CVERecord?id=CVE-2022-48687 Référence CVE CVE-2022-48688 https://www.cve.org/CVERecord?id=CVE-2022-48688 Référence CVE CVE-2022-48692 https://www.cve.org/CVERecord?id=CVE-2022-48692 Référence CVE CVE-2022-48693 https://www.cve.org/CVERecord?id=

Official advisory

CERT-FR · French · CERTFR-2024-AVI-0526Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-48632 Référence CVE CVE-2022-48633 https://www.cve.org/CVERecord?id=CVE-2022-48633 Référence CVE CVE-2022-48634 https://www.cve.org/CVERecord?id=CVE-2022-48634 Référence CVE CVE-2022-48636 https://www.cve.org/CVERecord?id=CVE-2022-48636 Référence CVE CVE-2022-48650 https://www.cve.org/CVERecord?id=CVE-2022-48650 Référence CVE CVE-2022-48651 https://www.cve.org/CVERecord?id=CVE-2022-48651 Référence CVE CVE-2022-48652 https://www.cve.org/CVERecord?id=CVE-2022-48652 Référence CVE CVE-2022-48662 https://www.cve.org/CVERecord?id=CVE-2022-48662 Référence CVE CVE-2022-48669 https://www.cve.org/CVERecord?id=CVE-2022-48669 Référence CVE CVE-2022-48671 https://www.cve.org/CVERecord?id=CVE-2022-48671 Référence CVE CVE-2022-48672 https://www.cve.org/CVERecord?id=CVE-2022-48672 Référence CVE CVE-2022-48673 https://www.cve.org/CVERecord?id=CVE-2022-48673 Référence CVE CVE-2022-48675 https://www.cve.org/CVERecord?id=CVE-2022-48675 Référence CVE CVE-2022-48686 https://www.cve.org/CVERecord?id=CVE-2022-48686 Référence CVE CVE-2022-48687 https://www.cve.org/CVERecord?id=CVE-2022-48687 Référence CVE CVE-2022-48688 https://www.cve.org/CVERecord?id=CVE-2022-48688 Référence CVE CVE-2022-48689 https://www.cve.org/CVERecord?id=CVE-2022-48689 Référence CVE CVE-2022-48691 https://www.cve.org/CVERecord?id=

Official advisory

CERT-FR · French · CERTFR-2024-AVI-0496Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-20132 Référence CVE CVE-2022-48632 https://www.cve.org/CVERecord?id=CVE-2022-48632 Référence CVE CVE-2022-48633 https://www.cve.org/CVERecord?id=CVE-2022-48633 Référence CVE CVE-2022-48634 https://www.cve.org/CVERecord?id=CVE-2022-48634 Référence CVE CVE-2022-48636 https://www.cve.org/CVERecord?id=CVE-2022-48636 Référence CVE CVE-2022-48650 https://www.cve.org/CVERecord?id=CVE-2022-48650 Référence CVE CVE-2022-48652 https://www.cve.org/CVERecord?id=CVE-2022-48652 Référence CVE CVE-2022-48662 https://www.cve.org/CVERecord?id=CVE-2022-48662 Référence CVE CVE-2022-48669 https://www.cve.org/CVERecord?id=CVE-2022-48669 Référence CVE CVE-2022-48671 https://www.cve.org/CVERecord?id=CVE-2022-48671 Référence CVE CVE-2022-48672 https://www.cve.org/CVERecord?id=CVE-2022-48672 Référence CVE CVE-2022-48673 https://www.cve.org/CVERecord?id=CVE-2022-48673 Référence CVE CVE-2022-48675 https://www.cve.org/CVERecord?id=CVE-2022-48675 Référence CVE CVE-2022-48686 https://www.cve.org/CVERecord?id=CVE-2022-48686 Référence CVE CVE-2022-48687 https://www.cve.org/CVERecord?id=CVE-2022-48687 Référence CVE CVE-2022-48688 https://www.cve.org/CVERecord?id=CVE-2022-48688 Référence CVE CVE-2022-48689 https://www.cve.org/CVERecord?id=CVE-2022-48689 Référence CVE CVE-2022-48691 https://www.cve.org/CVERecord?id=

Official advisory

CERT-FR · French · CERTFR-2024-AVI-0420Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-48656 Référence CVE CVE-2022-48657 https://www.cve.org/CVERecord?id=CVE-2022-48657 Référence CVE CVE-2022-48658 https://www.cve.org/CVERecord?id=CVE-2022-48658 Référence CVE CVE-2022-48659 https://www.cve.org/CVERecord?id=CVE-2022-48659 Référence CVE CVE-2022-48660 https://www.cve.org/CVERecord?id=CVE-2022-48660 Référence CVE CVE-2022-48662 https://www.cve.org/CVERecord?id=CVE-2022-48662 Référence CVE CVE-2022-48663 https://www.cve.org/CVERecord?id=CVE-2022-48663 Référence CVE CVE-2022-48667 https://www.cve.org/CVERecord?id=CVE-2022-48667 Référence CVE CVE-2022-48668 https://www.cve.org/CVERecord?id=CVE-2022-48668 Référence CVE CVE-2022-48671 https://www.cve.org/CVERecord?id=CVE-2022-48671 Référence CVE CVE-2022-48672 https://www.cve.org/CVERecord?id=CVE-2022-48672 Référence CVE CVE-2022-48673 https://www.cve.org/CVERecord?id=CVE-2022-48673 Référence CVE CVE-2022-48675 https://www.cve.org/CVERecord?id=CVE-2022-48675 Référence CVE CVE-2022-48686 https://www.cve.org/CVERecord?id=CVE-2022-48686 Référence CVE CVE-2022-48687 https://www.cve.org/CVERecord?id=CVE-2022-48687 Référence CVE CVE-2022-48688 https://www.cve.org/CVERecord?id=CVE-2022-48688 Référence CVE CVE-2022-48690 https://www.cve.org/CVERecord?id=CVE-2022-48690 Référence CVE CVE-2022-48692 https://www.cve.org/CVERecord?id=

Official advisory

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Patch available
Affected: e446300968c6bd25d9cd6c33b9600780a39b3975 < 321488cfac7d0eb6d97de467015ff754f85813ff; 59c6902a96b4439e07c25ef86a4593bea5481c3b < 07191f984842d50020789ff14c75da436a7f46a9; dee1e2b18cf5426eed985512ccc6636ec69dbdd6 < 9f267393b036f1470fb12fb892d59e7ff8aeb58d; 3bf4bf54069f9b62a54988e5d085023c17a66c90 < 5db17805b6ba4c34dab303f49aea3562fc25af75; c0deb027c99c099aa6b831e326bfba802b25e774 < 99bc25748e394d17f9e8b10cc7f273b8e64c1c7e; 4f7e7236435ca0abe005c674ebd6892c6e83aeb3 < 43626dade36fa74d3329046f4ae2d7fdefe401c6; 5.4.213 < 5.4.215; 5.10.143 < 5.10.145
Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action: Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround: No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.

Evidence and provenance

Published 3 May 2024 · Last source change 11 May 2026, 18:44 UTC · CWE-667 · Improper Locking

CVE recordCVE.org · 5.2

CVSS sourceNIST NVD

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-08-14

European sourceENISA EUVD · EUVD-2022-51366

Product sourceCNA

Remediation sourceCVE/CNA references

CWE sourceCISA ADP

NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates →

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

2024-05-03CVE published

2026-05-11Fixed release or patch reference recorded

ENISA EUVD · EUVD-2022-51366↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

cgroup: Add missing cpus_read_lock() to cgroup_attach_task_all()

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

ENISA European Vulnerability Database

EUVD-2022-51366

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication

cgroup: Add missing cpus_read_lock() to cgroup_attach_task_all()

National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

EUVD-2022-51366

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.