{"uuid": "dfbf1c1c-d29e-45eb-9411-cd8bf925ad82", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "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"}