CVERadar
HIGH · CVSS 3.1 7.8CISA KEV · added 2026-06-02Metasploit modulePublic PoCEPSS 5.53% (p93)Threat level 56

CVE-2022-0492: Linux Kernel Improper Authentication Vulnerability

Linux · Kernel · NVD published 2022-03-04 · posted 2026-06-02 · last modified 2026-06-17

What it is

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.

WeaknessCWE-287CWE-862
CVSS vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (source: [email protected])
CISA due date2026-06-05 (for US federal agencies under BOD; a good deadline for everyone)
ATT&CK tacticsInitial Access → Persistence → Privilege Escalation → Stealth

Exploitation evidence

First exploit evidence seen: 2022-02-04 (earliest date across the sources below).

Exploited in the wild

  • CISA KEV: listed since 2026-06-02. Source

Public exploit code

Metasploit

GitHub proof-of-concept repositories

8 public repositories from 8 accounts, first seen 2022-03-03. Most starred: PaloAltoNetworks/can-ctr-escape-cve-2022-0492 (46 stars), view repository.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: CISA KEV · Rapid7 Metasploit Framework module metadata · nomi-sec/PoC-in-GitHub.

Defend the Chain

The attack chain for CVE-2022-0492 laid across the MITRE ATT&CK Enterprise tactics. Solid cards come from the MITRE CTID KEV mappings; dashed cards are inferred by CVERadar from the CWE or description. Correct defences are real ATT&CK mitigations for that technique.

Threat level 56/100
Defender level 1 · 0 XP
Chain links broken: 0/3

Reconnaissance

Resource Development

Initial Access

Execution

Persistence

Privilege Escalation

Stealth

Defense Impairment

Credential Access

Discovery

Lateral Movement

Collection

Command and Control

Exfiltration

Impact

Pick a red technique card on the board, then choose the defence that stops it.

Defend against T1190 Exploit Public-Facing Application Inferred

Inferred from CWE CWE-287

How to fix it

CISA required action

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. (source: CISA KEV)

Fixed versions

  • linux linux kernel: upgrade to 4.9.301 or later (affected from 2.6.24)
  • linux linux kernel: upgrade to 4.14.266 or later (affected from 4.10)
  • linux linux kernel: upgrade to 4.19.229 or later (affected from 4.15)
  • linux linux kernel: upgrade to 5.4.177 or later (affected from 4.20)
  • linux linux kernel: upgrade to 5.10.97 or later (affected from 5.5)
  • linux linux kernel: upgrade to 5.15.20 or later (affected from 5.11)
  • linux linux kernel: upgrade to 5.16.6 or later (affected from 5.16)

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

MITRE ATT&CK mitigations for this chain

  • M1048 Application Isolation and Sandboxing (for T1190, T1068) : Application isolation will limit what other processes and system features the exploited target can access.
  • M1037 Filter Network Traffic (for T1190) : Restrict outbound network traffic from public-facing servers to prevent unauthorized connections from initiating communications with attacker-controlled infrastructure. While this may not prevent the initial exploitation, it limits the attacker's ability to verify and control the compromised server post-exploit, reduci
  • M1030 Network Segmentation (for T1190) : Segment externally facing servers and services from the rest of the network with a DMZ or on separate hosting infrastructure.
  • M1016 Vulnerability Scanning (for T1190) : Regularly scan externally facing systems for vulnerabilities and establish procedures to rapidly patch systems when critical vulnerabilities are discovered through scanning and through public disclosure.
  • M1026 Privileged Account Management (for T1190, T1078) : Use least privilege for service accounts will limit what permissions the exploited process gets on the rest of the system.
  • M1050 Exploit Protection (for T1190, T1068) : Web Application Firewalls may be used to limit exposure of applications to prevent exploit traffic from reaching the application.
  • M1035 Limit Access to Resource Over Network (for T1190) : Ensure that all publicly exposed services are actually intended to be so, and restrict access to any that should only be available internally.
  • M1051 Update Software (for T1190, T1068) : Update software regularly by employing patch management for externally exposed applications.
  • M1027 Password Policies (for T1078) : Applications and appliances that utilize default username and password should be changed immediately after the installation, and before deployment to a production environment. When possible, applications that use SSH keys should be updated periodically and properly secured. Policies should minimize (if not eliminate)
  • M1018 User Account Management (for T1078) : Regularly audit user accounts for activity and deactivate or remove any that are no longer needed.

Detection Generic guidance

  • Initial Access: Alert on unusual requests to the affected service (odd paths, oversized payloads, exploit strings) in WAF, reverse-proxy and application logs.
  • Persistence: Look for new files in web roots, new scheduled tasks/services, and new accounts created after the exposure window.
  • Privilege Escalation: Alert on processes gaining SYSTEM/root unexpectedly, and on exploitation crashes of privileged services.

Response checklist Generic guidance

  1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
  2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
  3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
  4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

Sources