{"uuid": "d5c5e54d-6c57-4542-b5f0-4e59e11baafb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50060", "type": "seen", "source": "https://t.me/cvedetector/8546", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50060 - Apache Io_uring Lock Lack of Overflow Defense\", \n  \"Content\": \"CVE ID : CVE-2024-50060 \nPublished : Oct. 21, 2024, 8:15 p.m. | 16\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nio_uring: check if we need to reschedule during overflow flush  \n  \nIn terms of normal application usage, this list will always be empty.  \nAnd if an application does overflow a bit, it'll have a few entries.  \nHowever, nothing obviously prevents syzbot from running a test case  \nthat generates a ton of overflow entries, and then flushing them can  \ntake quite a while.  \n  \nCheck for needing to reschedule while flushing, and drop our locks and  \ndo so if necessary. There's no state to maintain here as overflows  \nalways prune from head-of-list, hence it's fine to drop and reacquire  \nthe locks at the end of the loop. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-21T22:42:54.000000Z"}