CVE-2022-1966: High severity Microsoft cbl2 kernel 5.15.48.1-2 vulnerability
REJECT DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2022-32250. Reason: This candidate is a duplicate of CVE-2022-32250. Notes: All CVE users should reference CVE-2022-32250 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage.
Other sources
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2022-32250. Reason: This candidate is a duplicate of CVE-2022-32250. Notes: All CVE users should reference CVE-2022-32250 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage.
— NVD
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
If unprivileged users do not need to create namespaces, disable this ability by setting kernel.unprivileged_userns_clone=0 with sysctl and persist it in /etc/sysctl.d/99-disable-unpriv-userns.conf.
Linux kernel kernel.unprivileged_userns_clone = 0
Event History
Frequently Asked Questions
What is CVE-2022-1966?
CVE-2022-1966 is a duplicate candidate and users should reference CVE-2022-32250 instead.
What should I do if I come across CVE-2022-1966?
If you come across CVE-2022-1966, please reference CVE-2022-32250 instead.
What is the impact of CVE-2022-1966?
The impact of CVE-2022-1966 is the same as CVE-2022-32250, which should be referenced for more information.
Where can I find more information about CVE-2022-32250?
More information about CVE-2022-32250 can be found at [CVE-2022-32250](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32250).
Is there a fix available for CVE-2022-1966?
Please refer to the mitigation steps provided for CVE-2022-32250 to address this vulnerability.