{"uuid": "97f631ec-8b00-40f5-b83d-54f8a81b7f15", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47717", "type": "seen", "source": "https://t.me/cvedetector/8456", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-47717 - RISC-V KVM PMU Snapshot NULL Pointer Crash\", \n  \"Content\": \"CVE ID : CVE-2024-47717 \nPublished : Oct. 21, 2024, 12:15 p.m. | 41\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nRISC-V: KVM: Don't zero-out PMU snapshot area before freeing data  \n  \nWith the latest Linux-6.11-rc3, the below NULL pointer crash is observed  \nwhen SBI PMU snapshot is enabled for the guest and the guest is forcefully  \npowered-off.  \n  \n  Unable to handle kernel NULL pointer dereference at virtual address 0000000000000508  \n  Oops [#1]  \n  Modules linked in: kvm  \n  CPU: 0 UID: 0 PID: 61 Comm: term-poll Not tainted 6.11.0-rc3-00018-g44d7178dd77a #3  \n  Hardware name: riscv-virtio,qemu (DT)  \n  epc : __kvm_write_guest_page+0x94/0xa6 [kvm]  \n   ra : __kvm_write_guest_page+0x54/0xa6 [kvm]  \n  epc : ffffffff01590e98 ra : ffffffff01590e58 sp : ffff8f80001f39b0  \n   gp : ffffffff81512a60 tp : ffffaf80024872c0 t0 : ffffaf800247e000  \n   t1 : 00000000000007e0 t2 : 0000000000000000 s0 : ffff8f80001f39f0  \n   s1 : 00007fff89ac4000 a0 : ffffffff015dd7e8 a1 : 0000000000000086  \n   a2 : 0000000000000000 a3 : ffffaf8000000000 a4 : ffffaf80024882c0  \n   a5 : 0000000000000000 a6 : ffffaf800328d780 a7 : 00000000000001cc  \n   s2 : ffffaf800197bd00 s3 : 00000000000828c4 s4 : ffffaf800248c000  \n   s5 : ffffaf800247d000 s6 : 0000000000001000 s7 : 0000000000001000  \n   s8 : 0000000000000000 s9 : 00007fff861fd500 s10: 0000000000000001  \n   s11: 0000000000800000 t3 : 00000000000004d3 t4 : 00000000000004d3  \n   t5 : ffffffff814126e0 t6 : ffffffff81412700  \n  status: 0000000200000120 badaddr: 0000000000000508 cause: 000000000000000d  \n  [] __kvm_write_guest_page+0x94/0xa6 [kvm]  \n  [] kvm_vcpu_write_guest+0x56/0x90 [kvm]  \n  [] kvm_pmu_clear_snapshot_area+0x42/0x7e [kvm]  \n  [] kvm_riscv_vcpu_pmu_deinit.part.0+0xe0/0x14e [kvm]  \n  [] kvm_riscv_vcpu_pmu_deinit+0x1a/0x24 [kvm]  \n  [] kvm_arch_vcpu_destroy+0x28/0x4c [kvm]  \n  [] kvm_destroy_vcpus+0x5a/0xda [kvm]  \n  [] kvm_arch_destroy_vm+0x14/0x28 [kvm]  \n  [] kvm_destroy_vm+0x168/0x2a0 [kvm]  \n  [] kvm_put_kvm+0x3c/0x58 [kvm]  \n  [] kvm_vm_release+0x22/0x2e [kvm]  \n  \nClearly, the kvm_vcpu_write_guest() function is crashing because it is  \nbeing called from kvm_pmu_clear_snapshot_area() upon guest tear down.  \n  \nTo address the above issue, simplify the kvm_pmu_clear_snapshot_area() to  \nnot zero-out PMU snapshot area from kvm_pmu_clear_snapshot_area() because  \nthe guest is anyway being tore down.  \n  \nThe kvm_pmu_clear_snapshot_area() is also called when guest changes  \nPMU snapshot area of a VCPU but even in this case the previous PMU  \nsnaphsot area must not be zeroed-out because the guest might have  \nreclaimed the pervious PMU snapshot area for some other purpose. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-21T15:09:37.000000Z"}