https://vulnerability.circl.lu/sightings/feed 2026-05-08T20:40:31.448234+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/ad6ff299-0148-4e4f-a6be-e2fba22dc0d4/export 2026-05-08T20:40:31.810698+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "ad6ff299-0148-4e4f-a6be-e2fba22dc0d4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-23134", "type": "seen", "source": "https://t.me/cvedetector/23116", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-23134 - ALSA Timer Mutex Deadlock Vulnerability\", \n \"Content\": \"CVE ID : CVE-2025-23134 \nPublished : April 16, 2025, 3:16 p.m. | 23\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nALSA: timer: Don't take register_mutex with copy_from/to_user() \n \nThe infamous mmap_lock taken in copy_from/to_user() can be often \nproblematic when it's called inside another mutex, as they might lead \nto deadlocks. \n \nIn the case of ALSA timer code, the bad pattern is with \nguard(mutex)(&register_mutex) that covers copy_from/to_user() -- which \nwas mistakenly introduced at converting to guard(), and it had been \ncarefully worked around in the past. \n \nThis patch fixes those pieces simply by moving copy_from/to_user() out \nof the register mutex lock again. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"16 Apr 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-16T17:43:37.000000Z"} 2025-04-16T17:43:37+00:00