{"vulnerability": "CVE-2024-45817", "sightings": [{"uuid": "dbbcd01a-47bf-45b1-848f-334c6fd43387", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-45817", "type": "seen", "source": "https://t.me/cvedetector/6306", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-45817 - Xen APIC races: Lock Deadlock via Recursive Error Interrupt\", \n  \"Content\": \"CVE ID : CVE-2024-45817 \nPublished : Sept. 25, 2024, 11:15 a.m. | 41\u00a0minutes ago \nDescription : In x86's APIC (Advanced Programmable Interrupt Controller) architecture,  \nerror conditions are reported in a status register.  Furthermore, the OS  \ncan opt to receive an interrupt when a new error occurs.  \n  \nIt is possible to configure the error interrupt with an illegal vector,  \nwhich generates an error when an error interrupt is raised.  \n  \nThis case causes Xen to recurse through vlapic_error().  The recursion  \nitself is bounded; errors accumulate in the the status register and only  \ngenerate an interrupt when a new status bit becomes set.  \n  \nHowever, the lock protecting this state in Xen will try to be taken  \nrecursively, and deadlock. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"25 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-25T14:19:23.000000Z"}]}