CVE-2022-48943

{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2022-48943", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2024-08-22T01:27:53.623Z", "datePublished": "2024-08-22T03:30:14.027Z", "dateUpdated": "2026-08-05T08:53:03.401Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-08-05T08:53:03.401Z"}, "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86/mmu: make apf token non-zero to fix bug\n\nIn current async pagefault logic, when a page is ready, KVM relies on\nkvm_arch_can_dequeue_async_page_present() to determine whether to deliver\na READY event to the Guest. This function test token value of struct\nkvm_vcpu_pv_apf_data, which must be reset to zero by Guest kernel when a\nREADY event is finished by Guest. If value is zero meaning that a READY\nevent is done, so the KVM can deliver another.\nBut the kvm_arch_setup_async_pf() may produce a valid token with zero\nvalue, which is confused with previous mention and may lead the loss of\nthis READY event.\n\nThis bug may cause task blocked forever in Guest:\n INFO: task stress:7532 blocked for more than 1254 seconds.\n Not tainted 5.10.0 #16\n \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\n task:stress state:D stack: 0 pid: 7532 ppid: 1409\n flags:0x00000080\n Call Trace:\n __schedule+0x1e7/0x650\n schedule+0x46/0xb0\n kvm_async_pf_task_wait_schedule+0xad/0xe0\n ? exit_to_user_mode_prepare+0x60/0x70\n __kvm_handle_async_pf+0x4f/0xb0\n ? asm_exc_page_fault+0x8/0x30\n exc_page_fault+0x6f/0x110\n ? asm_exc_page_fault+0x8/0x30\n asm_exc_page_fault+0x1e/0x30\n RIP: 0033:0x402d00\n RSP: 002b:00007ffd31912500 EFLAGS: 00010206\n RAX: 0000000000071000 RBX: ffffffffffffffff RCX: 00000000021a32b0\n RDX: 000000000007d011 RSI: 000000000007d000 RDI: 00000000021262b0\n RBP: 00000000021262b0 R08: 0000000000000003 R09: 0000000000000086\n R10: 00000000000000eb R11: 00007fefbdf2baa0 R12: 0000000000000000\n R13: 0000000000000002 R14: 000000000007d000 R15: 0000000000001000"}], "metrics": [{"cvssV3_1": {"version": "3.1", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H", "baseScore": 7.1, "baseSeverity": "HIGH"}, "scenarios": [{"lang": "en", "value": "AV:L - The bug is reached only when a KVM guest takes a paravirtual async page fault (KVM_RUN \u2192 faultin \u2192 kvm_arch_setup_async_pf), which requires local code execution inside a VM or local /dev/kvm use\u2014not remote packet processing.\nAC:L - On overcommitted KVM hosts (common cloud deployments) async PF is routinely exercised; token 0 is produced deterministically on vCPU 0 when (id<<12)==0, and concurrent READY completions that drop that event are driven by attacker/workload-controlled multi-threaded memory stress, as in the original hang report.\nPR:N - No host privileges are required\u2014an ordinary tenant VM triggers this via normal guest userspace page faults after the guest kernel enables MSR_KVM_ASYNC_PF_EN, matching other guest-triggerable KVM DoS scores (PR:N relative to the host).\nUI:N - No separate victim action is needed; guest memory accesses under host reclaim/async PF delivery alone hit the vulnerable token path.\nS:C - The vulnerable code is host KVM MMU/async-PF handling, but the impact is permanent denial of guest task/VM progress across the hypervisor\u2013guest (and nested L1/L2) security boundary, consistent with other host-KVM guest-availability DoS scorings.\nC:N - This is solely a confused zero token versus the READY-slot-empty sentinel causing a lost wakeup; there is no OOB read, UAF, or other disclosure primitive.\nI:N - No memory corruption, write primitive, or control-flow hijack occurs\u2014only failure to deliver a READY notification for a valid token value of zero.\nA:H - A lost READY leaves the guest task blocked forever in TASK_UNINTERRUPTIBLE (D state), which is a complete denial of that workload\u2019s availability and can stall nested guests depending on the hung threads."}]}], "affected": [{"product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["arch/x86/kvm/mmu/mmu.c"], "versions": [{"version": "2635b5c4a0e407b84f68e188c719f28ba0e9ae1b", "lessThan": "72fdfc75d4217b32363cc80def3de2cb3fef3f02", "status": "affected", "versionType": "git"}, {"version": "2635b5c4a0e407b84f68e188c719f28ba0e9ae1b", "lessThan": "4c3644b6c96c5daa5149e5abddc07234eea47c7c", "status": "affected", "versionType": "git"}, {"version": "2635b5c4a0e407b84f68e188c719f28ba0e9ae1b", "lessThan": "62040f5cd7d937de547836e747b6aa8212fec573", "status": "affected", "versionType": "git"}, {"version": "2635b5c4a0e407b84f68e188c719f28ba0e9ae1b", "lessThan": "6f3c1fc53d86d580d8d6d749c4af23705e4f6f79", "status": "affected", "versionType": "git"}]}, {"product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["arch/x86/kvm/mmu/mmu.c"], "versions": [{"version": "5.8", "status": "affected"}, {"version": "0", "lessThan": "5.8", "status": "unaffected", "versionType": "semver"}, {"version": "5.10.103", "lessThanOrEqual": "5.10.*", "status": "unaffected", "versionType": "semver"}, {"version": "5.15.26", "lessThanOrEqual": "5.15.*", "status": "unaffected", "versionType": "semver"}, {"version": "5.16.12", "lessThanOrEqual": "5.16.*", "status": "unaffected", "versionType": "semver"}, {"version": "5.17", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix"}]}], "cpeApplicability": [{"nodes": [{"operator": "OR", "negate": false, "cpeMatch": [{"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "5.8", "versionEndExcluding": "5.10.103"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "5.8", "versionEndExcluding": "5.15.26"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "5.8", "versionEndExcluding": "5.16.12"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "5.8", "versionEndExcluding": "5.17"}]}]}], "references": [{"url": "https://git.kernel.org/stable/c/72fdfc75d4217b32363cc80def3de2cb3fef3f02"}, {"url": "https://git.kernel.org/stable/c/4c3644b6c96c5daa5149e5abddc07234eea47c7c"}, {"url": "https://git.kernel.org/stable/c/62040f5cd7d937de547836e747b6aa8212fec573"}, {"url": "https://git.kernel.org/stable/c/6f3c1fc53d86d580d8d6d749c4af23705e4f6f79"}], "title": "KVM: x86/mmu: make apf token non-zero to fix bug", "x_generator": {"engine": "bippy-1.2.0"}}, "adp": [{"metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2022-48943", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "partial"}], "version": "2.0.3", "timestamp": "2024-09-10T15:33:08.943998Z"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2024-09-12T17:33:10.679Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2022-48943", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "partial"}], "version": "2.0.3", "timestamp": "2024-09-10T15:33:08.943998Z"}}}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2024-09-11T12:42:15.638Z"}}], "cna": {"title": "KVM: x86/mmu: make apf token non-zero to fix bug", "metrics": [{"cvssV3_1": {"version": "3.1", "baseScore": 7.1, "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H"}, "scenarios": [{"lang": "en", "value": "AV:L - The bug is reached only when a KVM guest takes a paravirtual async page fault (KVM_RUN \u2192 faultin \u2192 kvm_arch_setup_async_pf), which requires local code execution inside a VM or local /dev/kvm use\u2014not remote packet processing.\nAC:L - On overcommitted KVM hosts (common cloud deployments) async PF is routinely exercised; token 0 is produced deterministically on vCPU 0 when (id<<12)==0, and concurrent READY completions that drop that event are driven by attacker/workload-controlled multi-threaded memory stress, as in the original hang report.\nPR:N - No host privileges are required\u2014an ordinary tenant VM triggers this via normal guest userspace page faults after the guest kernel enables MSR_KVM_ASYNC_PF_EN, matching other guest-triggerable KVM DoS scores (PR:N relative to the host).\nUI:N - No separate victim action is needed; guest memory accesses under host reclaim/async PF delivery alone hit the vulnerable token path.\nS:C - The vulnerable code is host KVM MMU/async-PF handling, but the impact is permanent denial of guest task/VM progress across the hypervisor\u2013guest (and nested L1/L2) security boundary, consistent with other host-KVM guest-availability DoS scorings.\nC:N - This is solely a confused zero token versus the READY-slot-empty sentinel causing a lost wakeup; there is no OOB read, UAF, or other disclosure primitive.\nI:N - No memory corruption, write primitive, or control-flow hijack occurs\u2014only failure to deliver a READY notification for a valid token value of zero.\nA:H - A lost READY leaves the guest task blocked forever in TASK_UNINTERRUPTIBLE (D state), which is a complete denial of that workload\u2019s availability and can stall nested guests depending on the hung threads."}]}], "affected": [{"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "2635b5c4a0e407b84f68e188c719f28ba0e9ae1b", "lessThan": "72fdfc75d4217b32363cc80def3de2cb3fef3f02", "versionType": "git"}, {"status": "affected", "version": "2635b5c4a0e407b84f68e188c719f28ba0e9ae1b", "lessThan": "4c3644b6c96c5daa5149e5abddc07234eea47c7c", "versionType": "git"}, {"status": "affected", "version": "2635b5c4a0e407b84f68e188c719f28ba0e9ae1b", "lessThan": "62040f5cd7d937de547836e747b6aa8212fec573", "versionType": "git"}, {"status": "affected", "version": "2635b5c4a0e407b84f68e188c719f28ba0e9ae1b", "lessThan": "6f3c1fc53d86d580d8d6d749c4af23705e4f6f79", "versionType": "git"}], "programFiles": ["arch/x86/kvm/mmu/mmu.c"], "defaultStatus": "unaffected"}, {"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "5.8"}, {"status": "unaffected", "version": "0", "lessThan": "5.8", "versionType": "semver"}, {"status": "unaffected", "version": "5.10.103", "versionType": "semver", "lessThanOrEqual": "5.10.*"}, {"status": "unaffected", "version": "5.15.26", "versionType": "semver", "lessThanOrEqual": "5.15.*"}, {"status": "unaffected", "version": "5.16.12", "versionType": "semver", "lessThanOrEqual": "5.16.*"}, {"status": "unaffected", "version": "5.17", "versionType": "original_commit_for_fix", "lessThanOrEqual": "*"}], "programFiles": ["arch/x86/kvm/mmu/mmu.c"], "defaultStatus": "affected"}], "references": [{"url": "https://git.kernel.org/stable/c/72fdfc75d4217b32363cc80def3de2cb3fef3f02"}, {"url": "https://git.kernel.org/stable/c/4c3644b6c96c5daa5149e5abddc07234eea47c7c"}, {"url": "https://git.kernel.org/stable/c/62040f5cd7d937de547836e747b6aa8212fec573"}, {"url": "https://git.kernel.org/stable/c/6f3c1fc53d86d580d8d6d749c4af23705e4f6f79"}], "x_generator": {"engine": "bippy-1.2.0"}, "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86/mmu: make apf token non-zero to fix bug\n\nIn current async pagefault logic, when a page is ready, KVM relies on\nkvm_arch_can_dequeue_async_page_present() to determine whether to deliver\na READY event to the Guest. This function test token value of struct\nkvm_vcpu_pv_apf_data, which must be reset to zero by Guest kernel when a\nREADY event is finished by Guest. If value is zero meaning that a READY\nevent is done, so the KVM can deliver another.\nBut the kvm_arch_setup_async_pf() may produce a valid token with zero\nvalue, which is confused with previous mention and may lead the loss of\nthis READY event.\n\nThis bug may cause task blocked forever in Guest:\n INFO: task stress:7532 blocked for more than 1254 seconds.\n Not tainted 5.10.0 #16\n \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\n task:stress state:D stack: 0 pid: 7532 ppid: 1409\n flags:0x00000080\n Call Trace:\n __schedule+0x1e7/0x650\n schedule+0x46/0xb0\n kvm_async_pf_task_wait_schedule+0xad/0xe0\n ? exit_to_user_mode_prepare+0x60/0x70\n __kvm_handle_async_pf+0x4f/0xb0\n ? asm_exc_page_fault+0x8/0x30\n exc_page_fault+0x6f/0x110\n ? asm_exc_page_fault+0x8/0x30\n asm_exc_page_fault+0x1e/0x30\n RIP: 0033:0x402d00\n RSP: 002b:00007ffd31912500 EFLAGS: 00010206\n RAX: 0000000000071000 RBX: ffffffffffffffff RCX: 00000000021a32b0\n RDX: 000000000007d011 RSI: 000000000007d000 RDI: 00000000021262b0\n RBP: 00000000021262b0 R08: 0000000000000003 R09: 0000000000000086\n R10: 00000000000000eb R11: 00007fefbdf2baa0 R12: 0000000000000000\n R13: 0000000000000002 R14: 000000000007d000 R15: 0000000000001000"}], "cpeApplicability": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "5.10.103", "versionStartIncluding": "5.8"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "5.15.26", "versionStartIncluding": "5.8"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "5.16.12", "versionStartIncluding": "5.8"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "5.17", "versionStartIncluding": "5.8"}], "operator": "OR"}]}], "providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-08-05T08:53:03.401Z"}}}, "cveMetadata": {"cveId": "CVE-2022-48943", "state": "PUBLISHED", "dateUpdated": "2026-08-05T08:53:03.401Z", "dateReserved": "2024-08-22T01:27:53.623Z", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "datePublished": "2024-08-22T03:30:14.027Z", "assignerShortName": "Linux"}, "dataVersion": "5.2"}

{"affected": [{"affectedData": [{"defaultStatus": "unaffected", "product": "Linux", "programFiles": ["arch/x86/kvm/mmu/mmu.c"], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [{"lessThan": "72fdfc75d4217b32363cc80def3de2cb3fef3f02", "status": "affected", "version": "2635b5c4a0e407b84f68e188c719f28ba0e9ae1b", "versionType": "git"}, {"lessThan": "4c3644b6c96c5daa5149e5abddc07234eea47c7c", "status": "affected", "version": "2635b5c4a0e407b84f68e188c719f28ba0e9ae1b", "versionType": "git"}, {"lessThan": "62040f5cd7d937de547836e747b6aa8212fec573", "status": "affected", "version": "2635b5c4a0e407b84f68e188c719f28ba0e9ae1b", "versionType": "git"}, {"lessThan": "6f3c1fc53d86d580d8d6d749c4af23705e4f6f79", "status": "affected", "version": "2635b5c4a0e407b84f68e188c719f28ba0e9ae1b", "versionType": "git"}]}, {"defaultStatus": "affected", "product": "Linux", "programFiles": ["arch/x86/kvm/mmu/mmu.c"], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [{"status": "affected", "version": "5.8"}, {"lessThan": "5.8", "status": "unaffected", "version": "0", "versionType": "semver"}, {"lessThanOrEqual": "5.10.*", "status": "unaffected", "version": "5.10.103", "versionType": "semver"}, {"lessThanOrEqual": "5.15.*", "status": "unaffected", "version": "5.15.26", "versionType": "semver"}, {"lessThanOrEqual": "5.16.*", "status": "unaffected", "version": "5.16.12", "versionType": "semver"}, {"lessThanOrEqual": "*", "status": "unaffected", "version": "5.17", "versionType": "original_commit_for_fix"}]}], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "matchCriteriaId": "7E2EF203-0F7F-41A9-9684-671AAD1D37A1", "versionEndExcluding": "5.10.103", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "matchCriteriaId": "9AB342AE-A62E-4947-A6EA-511453062B2B", "versionEndExcluding": "5.15.26", "versionStartIncluding": "5.11", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "matchCriteriaId": "C76BAB21-7F23-4AD8-A25F-CA7B262A2698", "versionEndExcluding": "5.16.12", "versionStartIncluding": "5.16", "vulnerable": true}], "negate": false, "operator": "OR"}]}], "cveTags": [], "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86/mmu: make apf token non-zero to fix bug\n\nIn current async pagefault logic, when a page is ready, KVM relies on\nkvm_arch_can_dequeue_async_page_present() to determine whether to deliver\na READY event to the Guest. This function test token value of struct\nkvm_vcpu_pv_apf_data, which must be reset to zero by Guest kernel when a\nREADY event is finished by Guest. If value is zero meaning that a READY\nevent is done, so the KVM can deliver another.\nBut the kvm_arch_setup_async_pf() may produce a valid token with zero\nvalue, which is confused with previous mention and may lead the loss of\nthis READY event.\n\nThis bug may cause task blocked forever in Guest:\n INFO: task stress:7532 blocked for more than 1254 seconds.\n Not tainted 5.10.0 #16\n \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\n task:stress state:D stack: 0 pid: 7532 ppid: 1409\n flags:0x00000080\n Call Trace:\n __schedule+0x1e7/0x650\n schedule+0x46/0xb0\n kvm_async_pf_task_wait_schedule+0xad/0xe0\n ? exit_to_user_mode_prepare+0x60/0x70\n __kvm_handle_async_pf+0x4f/0xb0\n ? asm_exc_page_fault+0x8/0x30\n exc_page_fault+0x6f/0x110\n ? asm_exc_page_fault+0x8/0x30\n asm_exc_page_fault+0x1e/0x30\n RIP: 0033:0x402d00\n RSP: 002b:00007ffd31912500 EFLAGS: 00010206\n RAX: 0000000000071000 RBX: ffffffffffffffff RCX: 00000000021a32b0\n RDX: 000000000007d011 RSI: 000000000007d000 RDI: 00000000021262b0\n RBP: 00000000021262b0 R08: 0000000000000003 R09: 0000000000000086\n R10: 00000000000000eb R11: 00007fefbdf2baa0 R12: 0000000000000000\n R13: 0000000000000002 R14: 000000000007d000 R15: 0000000000001000"}, {"lang": "es", "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: KVM: x86/mmu: haga que el token apf sea distinto de cero para corregir el error En la l\u00f3gica de error de p\u00e1gina as\u00edncrona actual, cuando una p\u00e1gina est\u00e1 lista, KVM se basa en kvm_arch_can_dequeue_async_page_present() para determinar si se debe entregar un evento LISTO para el Invitado. Esta funci\u00f3n prueba el valor del token de la estructura kvm_vcpu_pv_apf_data, que el kernel invitado debe restablecer a cero cuando el invitado finaliza un evento READY. Si el valor es cero, significa que se realiz\u00f3 un evento READY, por lo que el KVM puede entregar otro. Pero kvm_arch_setup_async_pf() puede producir un token v\u00e1lido con valor cero, lo que se confunde con la menci\u00f3n anterior y puede provocar la p\u00e9rdida de este evento READY. Este error puede causar que la tarea se bloquee para siempre en Guest: INFORMACI\u00d3N: tarea de estr\u00e9s:7532 bloqueada durante m\u00e1s de 1254 segundos. Not tainted 5.10.0 #16 \"echo 0 &gt; /proc/sys/kernel/hung_task_timeout_secs\" desactiva este mensaje. tarea:estr\u00e9s estado:D pila: 0 pid: 7532 ppid: 1409 banderas:0x00000080 Seguimiento de llamadas: __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: ffffffff RCX: 00000000021a32b0 RDX: 000000000007d011 RSI: 000000000007d000 RDI: 00000000021262b0 RBP: 00000000021262b0 R08: 03 R09: 0000000000000086 R10: 000000000000000000EB R11: 00007FEFBDF2BAA0 R12: 00000000000000000000 R13: 0000000000000002 R14: 000000000007D000 R15: 00000000001000"}], "id": "CVE-2022-48943", "lastModified": "2026-08-04T10:17:27.647", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "LOCAL", "availabilityImpact": "HIGH", "baseScore": 7.1, "baseSeverity": "HIGH", "confidentialityImpact": "NONE", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "CHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H", "version": "3.1"}, "exploitabilityScore": 2.5, "impactScore": 4.0, "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "type": "Secondary"}, {"cvssData": {"attackComplexity": "LOW", "attackVector": "LOCAL", "availabilityImpact": "HIGH", "baseScore": 7.8, "baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "version": "3.1"}, "exploitabilityScore": 1.8, "impactScore": 5.9, "source": "nvd@nist.gov", "type": "Primary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2022-48943", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "role": "CISA Coordinator", "timestamp": "2024-09-10T15:33:08.943998Z", "version": "2.0.3"}}]}, "published": "2024-08-22T04:15:19.027", "references": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "tags": ["Patch"], "url": "https://git.kernel.org/stable/c/4c3644b6c96c5daa5149e5abddc07234eea47c7c"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "tags": ["Patch"], "url": "https://git.kernel.org/stable/c/62040f5cd7d937de547836e747b6aa8212fec573"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "tags": ["Patch"], "url": "https://git.kernel.org/stable/c/6f3c1fc53d86d580d8d6d749c4af23705e4f6f79"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "tags": ["Patch"], "url": "https://git.kernel.org/stable/c/72fdfc75d4217b32363cc80def3de2cb3fef3f02"}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "vulnStatus": "Modified", "weaknesses": [{"description": [{"lang": "en", "value": "NVD-CWE-noinfo"}], "source": "nvd@nist.gov", "type": "Primary"}]}

{"affected_release": [{"advisory": "RHSA-2022:6460", "cpe": "cpe:/o:redhat:enterprise_linux:8", "package": "kernel-0:4.18.0-372.26.1.el8_6", "product_name": "Red Hat Enterprise Linux 8", "release_date": "2022-09-13T00:00:00Z"}, {"advisory": "RHSA-2022:7683", "cpe": "cpe:/o:redhat:enterprise_linux:8", "package": "kernel-0:4.18.0-425.3.1.el8", "product_name": "Red Hat Enterprise Linux 8", "release_date": "2022-11-08T00:00:00Z"}, {"advisory": "RHSA-2022:6003", "cpe": "cpe:/a:redhat:enterprise_linux:9", "package": "kernel", "product_name": "Red Hat Enterprise Linux 9", "release_date": "2022-08-09T00:00:00Z"}, {"advisory": "RHSA-2022:8267", "cpe": "cpe:/a:redhat:enterprise_linux:9", "package": "kernel-0:5.14.0-162.6.1.el9_1", "product_name": "Red Hat Enterprise Linux 9", "release_date": "2022-11-15T00:00:00Z"}, {"advisory": "RHSA-2022:6003", "cpe": "cpe:/o:redhat:enterprise_linux:9", "package": "kernel", "product_name": "Red Hat Enterprise Linux 9", "release_date": "2022-08-09T00:00:00Z"}, {"advisory": "RHSA-2022:8267", "cpe": "cpe:/o:redhat:enterprise_linux:9", "package": "kernel-0:5.14.0-162.6.1.el9_1", "product_name": "Red Hat Enterprise Linux 9", "release_date": "2022-11-15T00:00:00Z"}, {"advisory": "RHSA-2022:6460", "cpe": "cpe:/o:redhat:rhev_hypervisor:4.4::el8", "package": "kernel-0:4.18.0-372.26.1.el8_6", "product_name": "Red Hat Virtualization 4 for Red Hat Enterprise Linux 8", "release_date": "2022-09-13T00:00:00Z"}], "bugzilla": {"description": "kernel: KVM: x86/mmu: make apf token non-zero to fix bug", "id": "2307199", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2307199"}, "csaw": false, "cvss3": {"cvss3_base_score": "5.5", "cvss3_scoring_vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H", "status": "verified"}, "cwe": "CWE-367", "details": ["In the Linux kernel, the following vulnerability has been resolved:\nKVM: x86/mmu: make apf token non-zero to fix bug\nIn current async pagefault logic, when a page is ready, KVM relies on\nkvm_arch_can_dequeue_async_page_present() to determine whether to deliver\na READY event to the Guest. This function test token value of struct\nkvm_vcpu_pv_apf_data, which must be reset to zero by Guest kernel when a\nREADY event is finished by Guest. If value is zero meaning that a READY\nevent is done, so the KVM can deliver another.\nBut the kvm_arch_setup_async_pf() may produce a valid token with zero\nvalue, which is confused with previous mention and may lead the loss of\nthis READY event.\nThis bug may cause task blocked forever in Guest:\nINFO: task stress:7532 blocked for more than 1254 seconds.\nNot tainted 5.10.0 #16\n\"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\ntask:stress state:D stack: 0 pid: 7532 ppid: 1409\nflags:0x00000080\nCall Trace:\n__schedule+0x1e7/0x650\nschedule+0x46/0xb0\nkvm_async_pf_task_wait_schedule+0xad/0xe0\n? exit_to_user_mode_prepare+0x60/0x70\n__kvm_handle_async_pf+0x4f/0xb0\n? asm_exc_page_fault+0x8/0x30\nexc_page_fault+0x6f/0x110\n? asm_exc_page_fault+0x8/0x30\nasm_exc_page_fault+0x1e/0x30\nRIP: 0033:0x402d00\nRSP: 002b:00007ffd31912500 EFLAGS: 00010206\nRAX: 0000000000071000 RBX: ffffffffffffffff RCX: 00000000021a32b0\nRDX: 000000000007d011 RSI: 000000000007d000 RDI: 00000000021262b0\nRBP: 00000000021262b0 R08: 0000000000000003 R09: 0000000000000086\nR10: 00000000000000eb R11: 00007fefbdf2baa0 R12: 0000000000000000\nR13: 0000000000000002 R14: 000000000007d000 R15: 0000000000001000", "A hang vulnerability is possible in the Linux kernel in arch/x86/kvm/mmu/mmu.c. This issue may lead to compromised availability."], "name": "CVE-2022-48943", "package_state": [{"cpe": "cpe:/o:redhat:enterprise_linux:6", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 6"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Will not fix", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 9"}], "public_date": "2024-08-22T00:00:00Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2022-48943\nhttps://nvd.nist.gov/vuln/detail/CVE-2022-48943\nhttps://lore.kernel.org/linux-cve-announce/2024082227-CVE-2022-48943-8e11@gregkh/T"], "statement": "This issue is fixed in RHEL-9.0 and above (including 8.10):\n~~~\nin (rhel-9.1, rhel-9.2, rhel-9.3, rhel-9.4, rhel-9.5) KVM: x86/mmu: make apf token non-zero to fix bug\nin (rhel-8.7, rhel-8.8, rhel-8.9, rhel-8.10) KVM: x86/mmu: make apf token non-zero to fix bug\nin (rhel-9.0) KVM: x86/mmu: make apf token non-zero to fix bug\nin (rhel-8.6) KVM: x86/mmu: make apf token non-zero to fix bug\n~~~\nPlease note that while RHEL-9 kernel-rt still appears as affected, it has been fixed in the same RHSA as RHEL-9 kernel. This is because from RHEL-9.3 onwards, the kernel and kernel-rt fixes are bundled together in a single errata.", "threat_severity": "Moderate"}

{}