[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-DEBIAN-CVE-2022-48943":6},{"stargazers_count":4,"fetched_at":5},7,"2026-06-04T02:53:27.892Z",{"id":7,"descriptions":8,"cisa":9,"weaknesses":10,"exploits":11,"aliases":12,"duplicate_of":9,"upstream":13,"downstream":16,"duplicates":17,"related":18,"reserved_at":9,"published_at":19,"modified_at":20,"state":9,"summary":21,"references_raw":23,"kevs":30,"epss":9,"epss_history":31,"metrics":32,"affected":39},"DEBIAN-CVE-2022-48943","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",null,[],[],[],[14],{"_key":15},"CVE-2022-48943",[],[],[],"2024-08-22T04:15:19.027Z","2026-04-28T20:24:59.628637Z",{"cisa_kev":22,"cisa_ransomware":22,"cisa_vendor":9,"epss_severity":9,"epss_score":9,"severity":9,"severity_score":9,"severity_version":9,"severity_source":9,"severity_vector":9,"severity_status":9},false,[24],{"url":25,"sources":26,"tags":28},"https://security-tracker.debian.org/tracker/CVE-2022-48943",[27],"osv_debian",[29],"Advisory",[],[],[33],{"source":27,"cvss_v2_0":9,"cvss_v3_0":9,"cvss_v3_1":34,"cvss_v4_0":9},{"baseScore":35,"baseSeverity":9,"vectorString":36,"impactScore":37,"exploitabilityScore":38},7.8,"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",9.8,4.6,[40],{"ecosystem":41,"name":42,"vendor":43,"product":42,"cpe_part":9,"purl_type":44,"purl_namespace":43,"purl_name":42,"source":9,"versions":45},"Debian","linux","debian","deb",[46,52,55,56],{"version":47,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":50,"version_end_type":51,"fixed_in":9},"lt5_10_103_1",true,"ecosystem","5.10.103-1","excluding",{"version":53,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":54,"version_end_type":51,"fixed_in":9},"lt5_16_12_1","5.16.12-1",{"version":53,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":54,"version_end_type":51,"fixed_in":9},{"version":53,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":54,"version_end_type":51,"fixed_in":9}]