{"uuid": "4796bb69-1089-4465-9bed-b5a3cca8a216", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2022-49291", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/5429", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2022-49291\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nALSA: pcm: Fix races among concurrent hw_params and hw_free calls\n\nCurrently we have neither proper check nor protection against the\nconcurrent calls of PCM hw_params and hw_free ioctls, which may result\nin a UAF.  Since the existing PCM stream lock can't be used for\nprotecting the whole ioctl operations, we need a new mutex to protect\nthose racy calls.\n\nThis patch introduced a new mutex, runtime->buffer_mutex, and applies\nit to both hw_params and hw_free ioctl code paths.  Along with it, the\nboth functions are slightly modified (the mmap_count check is moved\ninto the state-check block) for code simplicity.\n\ud83d\udccf Published: 2025-02-26T01:56:27.986Z\n\ud83d\udccf Modified: 2025-02-26T01:56:27.986Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/a42aa926843acca96c0dfbde2e835b8137f2f092\n2. https://git.kernel.org/stable/c/9cb6c40a6ebe4a0cfc9d6a181958211682cffea9\n3. https://git.kernel.org/stable/c/fbeb492694ce0441053de57699e1e2b7bc148a69\n4. https://git.kernel.org/stable/c/0f6947f5f5208f6ebd4d76a82a4757e2839a23f8\n5. https://git.kernel.org/stable/c/33061d0fba51d2bf70a2ef9645f703c33fe8e438\n6. https://git.kernel.org/stable/c/0090c13cbbdffd7da079ac56f80373a9a1be0bf8\n7. https://git.kernel.org/stable/c/1bbf82d9f961414d6c76a08f7f843ea068e0ab7b\n8. https://git.kernel.org/stable/c/92ee3c60ec9fe64404dc035e7c41277d74aa26cb", "creation_timestamp": "2025-02-26T02:23:30.000000Z"}