CVE-2022-48943
KVM: x86/mmu: make apf token non-zero to fix bug
Reported by linux · Published August 22, 2024
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, which is confused with previous mention and may lead the loss of this READY event. This bug may cause task blocked forever in Guest: INFO: task stress:7532 blocked for more than 1254 seconds. Not tainted 5.10.0 #16 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:stress state:D stack: 0 pid: 7532 ppid: 1409 flags:0x00000080 Call Trace: __schedule+0x1e7/0x650 schedule+0x46/0xb0 kvm_async_pf_task_wait_schedule+0xad/0xe0 ? exit_to_user_mode_prepare+0x60/0x70 __kvm_handle_async_pf+0x4f/0xb0 ? asm_exc_page_fault+0x8/0x30 exc_page_fault+0x6f/0x110 ? asm_exc_page_fault+0x8/0x30 asm_exc_page_fault+0x1e/0x30 RIP: 0033:0x402d00 RSP: 002b:00007ffd31912500 EFLAGS: 00010206 RAX: 0000000000071000 RBX: ffffffffffffffff RCX: 00000000021a32b0 RDX: 000000000007d011 RSI: 000000000007d000 RDI: 00000000021262b0 RBP: 00000000021262b0 R08: 0000000000000003 R09: 0000000000000086 R10: 00000000000000eb R11: 00007fefbdf2baa0 R12: 0000000000000000 R13: 0000000000000002 R14: 000000000007d000 R15: 0000000000001000
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| linux_kernel | linux | 5.16.12, 5.15.26, 5.10.103 |
| Linux | Linux | 6f3c1fc53d86d580d8d6d749c4af23705e4f6f79, 62040f5cd7d937de547836e747b6aa8212fec573, 5.8 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 2635b5c4a0e407b84f68e188c719f28ba0e9ae1b, 2635b5c4a0e407b84f68e188c719f28ba0e9ae1b, 2635b5c4a0e407b84f68e188c719f28ba0e9ae1b |
| Linux | Linux | 5.8, 0, 5.10.103 |
| Linux | Linux | 5.17, 5.10.103, 5.15.26 |
| linux | linux_kernel | 5.8, 5.8, 5.8 |
Timeline
- Aug 22, 2024 CVE Published
- Sep 12, 2024 EPSS Score (29 in total, the first dated here)
- Mar 30, 2026 Distribution Patch (57 in total, the first dated here)
- Mar 30, 2026 Security Advisory (74 in total, the first dated here)
- May 23, 2026 Coalition ESS Score
- Aug 4, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2022-48943
vulnetix vdb fixes CVE-2022-48943
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2022-48943/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart