https://vulnerability.circl.lu/sightings/feed 2026-06-08T14:50:17.053624+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/dfbf1c1c-d29e-45eb-9411-cd8bf925ad82/export 2026-06-08T14:50:17.581061+00:00 Automation user https://cve.circl.lu/user/automation {"uuid": "dfbf1c1c-d29e-45eb-9411-cd8bf925ad82", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-45027", "type": "seen", "source": "https://t.me/cvedetector/5379", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-45027 - \"Huawei XHCI Uninitialized Pointer Derefence\"\", \n \"Content\": \"CVE ID : CVE-2024-45027 \nPublished : Sept. 11, 2024, 4:15 p.m. | 16\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nusb: xhci: Check for xhci->interrupters being allocated in xhci_mem_clearup() \n \nIf xhci_mem_init() fails, it calls into xhci_mem_cleanup() to mop \nup the damage. If it fails early enough, before xhci->interrupters \nis allocated but after xhci->max_interrupters has been set, which \nhappens in most (all?) cases, things get uglier, as xhci_mem_cleanup() \nunconditionally derefences xhci->interrupters. With prejudice. \n \nGate the interrupt freeing loop with a check on xhci->interrupters \nbeing non-NULL. \n \nFound while debugging a DMA allocation issue that led the XHCI driver \non this exact path. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"11 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-11T18:41:36.000000Z"} 2024-09-11T18:41:36+00:00 https://vulnerability.circl.lu/sighting/b623acd8-2ced-450a-a1a6-9c141fdb7bcb/export 2026-06-08T14:50:17.579064+00:00 Automation user https://cve.circl.lu/user/automation {"uuid": "b623acd8-2ced-450a-a1a6-9c141fdb7bcb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-45027", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15706", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-45027\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nusb: xhci: Check for xhci->interrupters being allocated in xhci_mem_clearup()\n\nIf xhci_mem_init() fails, it calls into xhci_mem_cleanup() to mop\nup the damage. If it fails early enough, before xhci->interrupters\nis allocated but after xhci->max_interrupters has been set, which\nhappens in most (all?) cases, things get uglier, as xhci_mem_cleanup()\nunconditionally derefences xhci->interrupters. With prejudice.\n\nGate the interrupt freeing loop with a check on xhci->interrupters\nbeing non-NULL.\n\nFound while debugging a DMA allocation issue that led the XHCI driver\non this exact path.\n\ud83d\udccf Published: 2024-09-11T15:13:59.032Z\n\ud83d\udccf Modified: 2025-05-09T08:06:06.586Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/3efb29f6a78d4746f958c1ab6cd7981c5762f03b\n2. https://git.kernel.org/stable/c/770cacc75b0091ece17349195d72133912c1ca7c\n3. https://git.kernel.org/stable/c/dcdb52d948f3a17ccd3fce757d9bd981d7c32039", "creation_timestamp": "2025-05-09T08:25:26.000000Z"} 2025-05-09T08:25:26+00:00