CVE-2022-48792 remediation guide
Linux Linux, linux kernel
In the Linux kernel, the following vulnerability has been resolved: scsi: pm8001: Fix use-after-free for aborted SSP/STP sas_task Currently a use-after-free may occur if a sas_task is aborted by the upper layer before we handle the I/O completion in mpi_ssp_completion() or mpi_sata_completion(). In this case, the following are the two steps in handling those I/O completions: - Call complete() to inform the upper layer handler of completion of the I/O. - Release driver resources associated with the sas_task in pm8001_ccb_task_free() call. When complete() is called, the upper layer may free t...
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: >= 869ddbdcae3b4fb83b99889abae31544c149b210 < fe9ac3eaa2e387a5742b380b73a5a6bc237bf184, >= 869ddbdcae3b4fb83b99889abae31544c149b210 < d9d93f32534a0a80a1c26bdb0746d90a7b19c2c2, >= 869ddbdcae3b4fb83b99889abae31544c149b210 < f61f9fccb2cb4bb275674a79d638704db6bc2171, >= 869ddbdcae3b4fb83b99889abae31544c149b210 < df7abcaa1246e2537ab4016077b5443bb3c09378, >= 4.15, < 5.10.102, >= 5.11 < 5.15.25, >= 5.16 < 5.16.11. 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.10.102, 5.15.25, 5.16.11. 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.