Skip to content
Cyber Threat
CTI Academy Sponsor CTI Academy
HIGH · CVSS 7.8 CISA Known Exploited Vulnerability

CVE-2022-0492

Linux Kernel Improper Authentication Vulnerability

Linux Kernel

A vulnerability was found in the Linux kernel’s cgroup_release_agent_write in the kernel/cgroup/cgroup-v1.c function. This flaw, under certain circumstances, allows the use of the cgroups v1 release_agent feature to escalate privileges and bypass the namespace isolation unexpectedly.

CVSS
7.8
HIGH
EPSS
5.5%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
3 Mar 2022
CWE-287, CWE-862

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 2 June 2026. US federal agencies were required to remediate it by 5 June 2026.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 5.5%, which is higher than 92.9% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Frequently asked questions

Is CVE-2022-0492 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2022-0492.

What does CVE-2022-0492 affect?

CVE-2022-0492 affects Linux Kernel. A vulnerability was found in the Linux kernel’s cgroup_release_agent_write in the kernel/cgroup/cgroup-v1.c function. This flaw, under certain circumstances, allows the use of the cgroups v1 release_agent feature to escalate privileges and bypass the namespace isolation unexpectedly.

How severe is CVE-2022-0492?

CVE-2022-0492 is rated HIGH with a CVSS base score of 7.8. EPSS puts the probability of exploitation in the next 30 days at 5.5%, higher than 92.9% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 5 June 2026.

How should organisations respond to CVE-2022-0492?

Apply the vendor patch for Linux Kernel as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.