Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2022-48943 | First vendor Publication | 2024-08-22 |
Vendor | Cve | Last vendor Modification | 2024-08-22 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | |||
---|---|---|---|
Overall CVSS Score | 7.8 | ||
Base Score | 7.8 | Environmental Score | 7.8 |
impact SubScore | 5.9 | Temporal Score | 7.8 |
Exploitabality Sub Score | 1.8 | ||
Attack Vector | Local | Attack Complexity | Low |
Privileges Required | Low | User Interaction | None |
Scope | Unchanged | Confidentiality Impact | High |
Integrity Impact | High | Availability Impact | High |
Calculate full CVSS 3.0 Vectors scores |
Security-Database Scoring CVSS v2
Cvss vector : | |||
---|---|---|---|
Cvss Base Score | N/A | Attack Range | N/A |
Cvss Impact Score | N/A | Attack Complexity | N/A |
Cvss Expoit Score | N/A | Authentication | N/A |
Calculate full CVSS 2.0 Vectors scores |
Detail
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: |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-48943 |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2025-01-08 02:47:33 |
|
2025-01-07 02:47:10 |
|
2024-12-25 02:45:56 |
|
2024-12-12 02:48:50 |
|
2024-11-22 02:46:14 |
|
2024-11-20 02:43:38 |
|
2024-11-14 02:43:31 |
|
2024-11-09 02:44:09 |
|
2024-10-26 02:41:55 |
|
2024-10-25 02:43:41 |
|
2024-10-23 02:43:05 |
|
2024-10-03 02:39:09 |
|
2024-10-02 02:37:32 |
|
2024-09-04 02:36:48 |
|
2024-08-23 02:48:02 |
|
2024-08-23 02:35:18 |
|
2024-08-23 00:27:27 |
|
2024-08-22 17:27:24 |
|
2024-08-22 09:27:25 |
|