CVE-2022-50234 remediation guide

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: io_uring/af_unix: defer registered files gc to io_uring release Instead of putting io_uring's registered files in unix_gc() we want it to be done by io_uring itself. The trick here is to consider io_uring registered files for cycle detection but not actually putting them down. Because io_uring can't register other ring instances, this will remove all refs to the ring file triggering the ->release path and clean up with io_ring_ctx_free(). [axboe: add kerneldoc comment to skb, fold in skb leak fix]

Open CVE record

ProductLinux Linux, linux kernel

Affected versions>= 6b06314c47e141031be043539900d80d2c7ba10f < 04df9719df1865f6770af9bc7880874af0e594b2, >= 6b06314c47e141031be043539900d80d2c7ba10f < c378c479c5175833bb22ff71974cda47d7b05401, >= 6b06314c47e141031be043539900d80d2c7ba10f < 813d8fe5d30388f73a21d3a2bf46b0a1fd72498c, >= 6b06314c47e141031be043539900d80d2c7ba10f < b4293c01ee0d0ecdd3cb5801e13f62271144667a, >= 6b06314c47e141031be043539900d80d2c7ba10f < 75e94c7e8859e58aadc15a98cc9704edff47d4f2, >= 6b06314c47e141031be043539900d80d2c7ba10f < 0091bfc81741b8d3aeb3b7ab8636f911b2de6e80, >= 5.1, >= 5.1 < 5.4.220, >= 5.5 < 5.10.150, >= 5.11 < 5.15.75, >= 5.16 < 5.19.17, >= 6.0 < 6.0.3

Fixed versions5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3

Priority basisReview · CVSS 7.8 · EPSS 0.15%

Identify the affected asset

Confirm whether Linux Linux, 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: >= 6b06314c47e141031be043539900d80d2c7ba10f < 04df9719df1865f6770af9bc7880874af0e594b2, >= 6b06314c47e141031be043539900d80d2c7ba10f < c378c479c5175833bb22ff71974cda47d7b05401, >= 6b06314c47e141031be043539900d80d2c7ba10f < 813d8fe5d30388f73a21d3a2bf46b0a1fd72498c, >= 6b06314c47e141031be043539900d80d2c7ba10f < b4293c01ee0d0ecdd3cb5801e13f62271144667a, >= 6b06314c47e141031be043539900d80d2c7ba10f < 75e94c7e8859e58aadc15a98cc9704edff47d4f2, >= 6b06314c47e141031be043539900d80d2c7ba10f < 0091bfc81741b8d3aeb3b7ab8636f911b2de6e80, >= 5.1, >= 5.1 < 5.4.220, >= 5.5 < 5.10.150, >= 5.11 < 5.15.75, >= 5.16 < 5.19.17, >= 6.0 < 6.0.3. Treat incomplete inventory results as unresolved.

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3. Preserve configuration and rollback material before change.

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.