CVE-2022-0492 remediation guide

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.

Open CVE record

ProductLinux Kernel

Affected versionskernel 5.17 rc3, >= 2.6.24 < 4.9.301, >= 4.10 < 4.14.266, >= 4.15 < 4.19.229, >= 4.20 < 5.4.177, >= 5.5 < 5.10.97, >= 5.11 < 5.15.20, >= 5.16 < 5.16.6, 5.17, 9.0, 10.0, 11.0, 8.0, 8.2, 4.0, 8.1, 14.04, 16.04, 18.04, 20.04

Fixed versions4.9.301, 4.14.266, 4.19.229, 5.4.177, 5.10.97, 5.15.20, 5.16.6

Priority basisImmediate · CVSS 7.8 · EPSS 5.53%

Identify the affected asset

Confirm whether Linux Kernel is installed, record the deployed version and installation path, and identify exposed interfaces.

Record the product name, package or appliance identifier, and installed version.
Identify internet-facing, administrative, API, and internal access paths.
Preserve the pre-change configuration and relevant service logs.

Validate the affected-version match

Compare the deployed version with the affected range: kernel 5.17 rc3, >= 2.6.24 < 4.9.301, >= 4.10 < 4.14.266, >= 4.15 < 4.19.229, >= 4.20 < 5.4.177, >= 5.5 < 5.10.97, >= 5.11 < 5.15.20, >= 5.16 < 5.16.6, 5.17, 9.0, 10.0, 11.0, 8.0, 8.2, 4.0, 8.1, 14.04, 16.04, 18.04, 20.04. Treat incomplete inventory results as unresolved.

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

Apply supported remediation

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

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

Confirm the expected version and package state.
Run a functional health check for critical service paths.
Review authentication, error, application, and security monitoring logs.
Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.