{"uuid": "1af11ae8-a007-4567-a210-12d31784be6e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56709", "type": "seen", "source": "https://t.me/cvedetector/13871", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56709 - \"Linux Kernel io_uring Task Work \u2013 Deadlock Prevention\"\", \n  \"Content\": \"CVE ID : CVE-2024-56709 \nPublished : Dec. 29, 2024, 9:15 a.m. | 24\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nio_uring: check if iowq is killed before queuing  \n  \ntask work can be executed after the task has gone through io_uring  \ntermination, whether it's the final task_work run or the fallback path.  \nIn this case, task work will find ->io_wq being already killed and  \nnull'ed, which is a problem if it then tries to forward the request to  \nio_queue_iowq(). Make io_queue_iowq() fail requests in this case.  \n  \nNote that it also checks PF_KTHREAD, because the user can first close  \na DEFER_TASKRUN ring and shortly after kill the task, in which case  \n->iowq check would race. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-29T10:41:23.000000Z"}