https://vulnerability.circl.lu/sightings/feed 2026-05-05T23:13:08.272307+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/9d0ca2ad-a389-41c9-a7b3-5d39f8404f9f/export 2026-05-05T23:13:08.680161+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "9d0ca2ad-a389-41c9-a7b3-5d39f8404f9f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-46692", "type": "seen", "source": "https://t.me/cvedetector/5547", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-46692 - Qualcomm qcom Firmware Atomic Sleep Mode Deadlock\", \n \"Content\": \"CVE ID : CVE-2024-46692 \nPublished : Sept. 13, 2024, 6:15 a.m. | 29\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nfirmware: qcom: scm: Mark get_wq_ctx() as atomic call \n \nCurrently get_wq_ctx() is wrongly configured as a standard call. When two \nSMC calls are in sleep and one SMC wakes up, it calls get_wq_ctx() to \nresume the corresponding sleeping thread. But if get_wq_ctx() is \ninterrupted, goes to sleep and another SMC call is waiting to be allocated \na waitq context, it leads to a deadlock. \n \nTo avoid this get_wq_ctx() must be an atomic call and can't be a standard \nSMC call. Hence mark get_wq_ctx() as a fast call. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"13 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-13T08:45:42.000000Z"} 2024-09-13T08:45:42+00:00