CVE-2022-50401 remediation guide

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: nfsd: under NFSv4.1, fix double svc_xprt_put on rpc_create failure On error situation `clp->cl_cb_conn.cb_xprt` should not be given a reference to the xprt otherwise both client cleanup and the error handling path of the caller call to put it. Better to delay handing over the reference to a later branch. [ 72.530665] refcount_t: underflow; use-after-free. [ 72.531933] WARNING: CPU: 0 PID: 173 at lib/refcount.c:28 refcount_warn_saturate+0xcf/0x120 [ 72.533075] Modules linked in: nfsd(OE) nfsv4(OE) nfsv3(OE) nfs(OE) lockd(OE)...

Open CVE record

ProductLinux Linux, linux kernel

Affected versions>= 69151594c72a1748cf93ae5b5fa68d5084253dce < 707bcca9616002d204091ca7c4d1d91151104332, >= 0c4fb76c4e711d9e4e70ddc6732310a17076175d < 15fc60aa5bdcf6d5f93000d3d00579fc67632ee0, >= 22c721560ef24003bcb9c3d9c358841dcfa4e212 < 9b4ae8c42d2ff09ed7c5832ccce5684c55e5ed23, >= e8cac2e3067e8587f8271c2177cc5ca924a61b54 < fddac3b4578d302ac9e51e7f03a9aae6254ae2a3, >= a4abc6b12eb1f7a533c2e7484cfa555454ff0977 < c1207219a4bfa50121c9345d5d165470d0a82531, >= a4abc6b12eb1f7a533c2e7484cfa555454ff0977 < a472f069ced8601979f53c13c0cf20236074ed46, >= a4abc6b12eb1f7a533c2e7484cfa555454ff0977 < e2f9f03e4537f3fcc8fd2bdd3248530c3477a371, >= a4abc6b12eb1f7a533c2e7484cfa555454ff0977 < d843ebd860c58a38e45527e8ec6516059f4c97f3, >= a4abc6b12eb1f7a533c2e7484cfa555454ff0977 < 3bc8edc98bd43540dbe648e4ef91f443d6d20a24, >= f5a50e848e4509448b8b91536b5d421722bf154b, >= c745f9ef3c8cbae70556131eaeaf0f64510243b7, >= 4.9.229 < 4.9.337, >= 4.14.186 < 4.14.303, >= 4.19.130 < 4.19.270, >= 5.4.49 < 5.4.229, >= 4.4.229 < 4.5, >= 5.7.6 < 5.8, >= 5.8, >= 5.7.6 < 5.10.163, >= 5.11 < 5.15.86

Fixed versions4.5, 4.9.337, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2

Priority basisReview · CVSS 7.8 · EPSS 0.40%

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: >= 69151594c72a1748cf93ae5b5fa68d5084253dce < 707bcca9616002d204091ca7c4d1d91151104332, >= 0c4fb76c4e711d9e4e70ddc6732310a17076175d < 15fc60aa5bdcf6d5f93000d3d00579fc67632ee0, >= 22c721560ef24003bcb9c3d9c358841dcfa4e212 < 9b4ae8c42d2ff09ed7c5832ccce5684c55e5ed23, >= e8cac2e3067e8587f8271c2177cc5ca924a61b54 < fddac3b4578d302ac9e51e7f03a9aae6254ae2a3, >= a4abc6b12eb1f7a533c2e7484cfa555454ff0977 < c1207219a4bfa50121c9345d5d165470d0a82531, >= a4abc6b12eb1f7a533c2e7484cfa555454ff0977 < a472f069ced8601979f53c13c0cf20236074ed46, >= a4abc6b12eb1f7a533c2e7484cfa555454ff0977 < e2f9f03e4537f3fcc8fd2bdd3248530c3477a371, >= a4abc6b12eb1f7a533c2e7484cfa555454ff0977 < d843ebd860c58a38e45527e8ec6516059f4c97f3, >= a4abc6b12eb1f7a533c2e7484cfa555454ff0977 < 3bc8edc98bd43540dbe648e4ef91f443d6d20a24, >= f5a50e848e4509448b8b91536b5d421722bf154b, >= c745f9ef3c8cbae70556131eaeaf0f64510243b7, >= 4.9.229 < 4.9.337, >= 4.14.186 < 4.14.303, >= 4.19.130 < 4.19.270, >= 5.4.49 < 5.4.229, >= 4.4.229 < 4.5, >= 5.7.6 < 5.8, >= 5.8, >= 5.7.6 < 5.10.163, >= 5.11 < 5.15.86. 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: 4.5, 4.9.337, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2. 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.