{"uuid": "1ce2c25c-7807-4b1b-894c-2f6027b846b7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-41080", "type": "seen", "source": "https://t.me/cvedetector/1862", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-41080 - Linux Kernel Io Uring Deadlock Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-41080 \nPublished : July 29, 2024, 3:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nio_uring: fix possible deadlock in io_register_iowq_max_workers()  \n  \nThe io_register_iowq_max_workers() function calls io_put_sq_data(),  \nwhich acquires the sqd->lock without releasing the uring_lock.  \nSimilar to the commit 009ad9f0c6ee (\"io_uring: drop ctx->uring_lock  \nbefore acquiring sqd->lock\"), this can lead to a potential deadlock  \nsituation.  \n  \nTo resolve this issue, the uring_lock is released before calling  \nio_put_sq_data(), and then it is re-acquired after the function call.  \n  \nThis change ensures that the locks are acquired in the correct  \norder, preventing the possibility of a deadlock. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-29T17:58:07.000000Z"}