https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Sat, 30 May 2026 17:16:23 +0000 https://vulnerability.circl.lu/sighting/91728044-e050-4130-bebd-748ba64e6d8e/export {"uuid": "91728044-e050-4130-bebd-748ba64e6d8e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-46864", "type": "seen", "source": "https://t.me/cvedetector/6521", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-46864 - Windows Hyper-V Hypervisor Kexec Crash Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-46864 \nPublished : Sept. 27, 2024, 1:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nx86/hyperv: fix kexec crash due to VP assist page corruption \n \ncommit 9636be85cc5b (\"x86/hyperv: Fix hyperv_pcpu_input_arg handling when \nCPUs go online/offline\") introduces a new cpuhp state for hyperv \ninitialization. \n \ncpuhp_setup_state() returns the state number if state is \nCPUHP_AP_ONLINE_DYN or CPUHP_BP_PREPARE_DYN and 0 for all other states. \nFor the hyperv case, since a new cpuhp state was introduced it would \nreturn 0. However, in hv_machine_shutdown(), the cpuhp_remove_state() call \nis conditioned upon \"hyperv_init_cpuhp > 0\". This will never be true and \nso hv_cpu_die() won't be called on all CPUs. This means the VP assist page \nwon't be reset. When the kexec kernel tries to setup the VP assist page \nagain, the hypervisor corrupts the memory region of the old VP assist page \ncausing a panic in case the kexec kernel is using that memory elsewhere. \nThis was originally fixed in commit dfe94d4086e4 (\"x86/hyperv: Fix kexec \npanic/hang issues\"). \n \nGet rid of hyperv_init_cpuhp entirely since we are no longer using a \ndynamic cpuhp state and use CPUHP_AP_HYPERV_ONLINE directly with \ncpuhp_remove_state(). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"27 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-27T15:53:27.000000Z"} {"uuid": "91728044-e050-4130-bebd-748ba64e6d8e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-46864", "type": "seen", "source": "https://t.me/cvedetector/6521", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-46864 - Windows Hyper-V Hypervisor Kexec Crash Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-46864 \nPublished : Sept. 27, 2024, 1:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nx86/hyperv: fix kexec crash due to VP assist page corruption \n \ncommit 9636be85cc5b (\"x86/hyperv: Fix hyperv_pcpu_input_arg handling when \nCPUs go online/offline\") introduces a new cpuhp state for hyperv \ninitialization. \n \ncpuhp_setup_state() returns the state number if state is \nCPUHP_AP_ONLINE_DYN or CPUHP_BP_PREPARE_DYN and 0 for all other states. \nFor the hyperv case, since a new cpuhp state was introduced it would \nreturn 0. However, in hv_machine_shutdown(), the cpuhp_remove_state() call \nis conditioned upon \"hyperv_init_cpuhp > 0\". This will never be true and \nso hv_cpu_die() won't be called on all CPUs. This means the VP assist page \nwon't be reset. When the kexec kernel tries to setup the VP assist page \nagain, the hypervisor corrupts the memory region of the old VP assist page \ncausing a panic in case the kexec kernel is using that memory elsewhere. \nThis was originally fixed in commit dfe94d4086e4 (\"x86/hyperv: Fix kexec \npanic/hang issues\"). \n \nGet rid of hyperv_init_cpuhp entirely since we are no longer using a \ndynamic cpuhp state and use CPUHP_AP_HYPERV_ONLINE directly with \ncpuhp_remove_state(). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"27 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-27T15:53:27.000000Z"} https://vulnerability.circl.lu/sighting/91728044-e050-4130-bebd-748ba64e6d8e/export Fri, 27 Sep 2024 15:53:27 +0000