SECUFOCUSNOW
Home›CVE index›CVE-2022-48943
Review reviewHigh

CVE-2022-48943

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...

CVSS
7.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2024.08.22
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.8

Vulnerability overview

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...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 2635b5c4a0e407b84f68e188c719f28ba0e9ae1b < 72fdfc75d4217b32363cc80def3de2cb3fef3f02, >= 2635b5c4a0e407b84f68e188c719f28ba0e9ae1b < 4c3644b6c96c5daa5149e5abddc07234eea47c7c, >= 2635b5c4a0e407b84f68e188c719f28ba0e9ae1b < 62040f5cd7d937de547836e747b6aa8212fec573, >= 2635b5c4a0e407b84f68e188c719f28ba0e9ae1b < 6f3c1fc53d86d580d8d6d749c4af23705e4f6f79, >= 5.8, < 5.10.103, >= 5.11 < 5.15.26, >= 5.16 < 5.16.12
Fixed versions
5.10.103, 5.15.26, 5.16.12

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available