CVE-2022-48943 remediation guide
Linux Linux, linux kernel
In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: make apf token non-zero to fix bug In current async pagefault logic, when a page is ready, KVM relies on kvm_arch_can_dequeue_async_page_present() to determine whether to deliver a READY event to the Guest. This function test token value of struct kvm_vcpu_pv_apf_data, which must be reset to zero by Guest kernel when a READY event is finished by Guest. If value is zero meaning that a READY event is done, so the KVM can deliver another. But the kvm_arch_setup_async_pf() may produce a valid token with zero value...
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: >= 2635b5c4a0e407b84f68e188c719f28ba0e9ae1b < 72fdfc75d4217b32363cc80def3de2cb3fef3f02, >= 2635b5c4a0e407b84f68e188c719f28ba0e9ae1b < 4c3644b6c96c5daa5149e5abddc07234eea47c7c, >= 2635b5c4a0e407b84f68e188c719f28ba0e9ae1b < 62040f5cd7d937de547836e747b6aa8212fec573, >= 2635b5c4a0e407b84f68e188c719f28ba0e9ae1b < 6f3c1fc53d86d580d8d6d749c4af23705e4f6f79, >= 5.8, < 5.10.103, >= 5.11 < 5.15.26, >= 5.16 < 5.16.12. 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.103, 5.15.26, 5.16.12. 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.