https://vulnerability.circl.lu/sightings/feed 2026-05-08T12:04:21.887135+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/82f31c22-c9dc-45ff-b1e4-a1e4cc6617ee/export 2026-05-08T12:04:22.236696+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "82f31c22-c9dc-45ff-b1e4-a1e4cc6617ee", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-46868", "type": "seen", "source": "https://t.me/cvedetector/6510", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-46868 - Android Linux Kernel Firmware Deadlock\", \n \"Content\": \"CVE ID : CVE-2024-46868 \nPublished : Sept. 27, 2024, 1:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nfirmware: qcom: uefisecapp: Fix deadlock in qcuefi_acquire() \n \nIf the __qcuefi pointer is not set, then in the original code, we would \nhold onto the lock. That means that if we tried to set it later, then \nit would cause a deadlock. Drop the lock on the error path. That's \nwhat all the callers are expecting. \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:12.000000Z"} 2024-09-27T15:53:12+00:00