https://vulnerability.circl.lu/sightings/feed 2026-06-02T07:06:56.766136+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/0fa2be01-ee51-45bb-bc3a-69a68a4e95bd/export 2026-06-02T07:06:57.129068+00:00 Automation user https://cve.circl.lu/user/automation {"uuid": "0fa2be01-ee51-45bb-bc3a-69a68a4e95bd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-44957", "type": "seen", "source": "https://t.me/cvedetector/4847", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-44957 - Xen Privcmd Spinlock Race Condition\", \n \"Content\": \"CVE ID : CVE-2024-44957 \nPublished : Sept. 4, 2024, 7:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nxen: privcmd: Switch from mutex to spinlock for irqfds \n \nirqfd_wakeup() gets EPOLLHUP, when it is called by \neventfd_release() by way of wake_up_poll(&ctx->wqh, EPOLLHUP), which \ngets called under spin_lock_irqsave(). We can't use a mutex here as it \nwill lead to a deadlock. \n \nFix it by switching over to a spin lock. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"04 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-04T21:56:27.000000Z"} 2024-09-04T21:56:27+00:00 https://vulnerability.circl.lu/sighting/2a37cd11-18c8-4706-9da2-f9171e24fbef/export 2026-06-02T07:06:57.126986+00:00 Alexandre Dulaunoy https://cve.circl.lu/user/adulau {"uuid": "2a37cd11-18c8-4706-9da2-f9171e24fbef", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-44957", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} 2025-12-03T14:14:49.267740+00:00