{"uuid": "8f6936f7-34a9-4d85-a08e-83fb628ce1db", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-42232", "type": "seen", "source": "https://t.me/cvedetector/2711", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42232 - Ceph Monitors Auth and Monmap Use-After-Free vulnerable Vulnerabilities\", \n  \"Content\": \"CVE ID : CVE-2024-42232 \nPublished : Aug. 7, 2024, 4:15 p.m. | 15\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nlibceph: fix race between delayed_work() and ceph_monc_stop()  \n  \nThe way the delayed work is handled in ceph_monc_stop() is prone to  \nraces with mon_fault() and possibly also finish_hunting().  Both of  \nthese can requeue the delayed work which wouldn't be canceled by any of  \nthe following code in case that happens after cancel_delayed_work_sync()  \nruns -- __close_session() doesn't mess with the delayed work in order  \nto avoid interfering with the hunting interval logic.  This part was  \nmissed in commit b5d91704f53e (\"libceph: behave in mon_fault() if  \ncur_mon auth and monc->monmap being  \nparticularly susceptible to quickly being reused.  \n  \nTo fix this:  \n  \n- clear monc->cur_mon and monc->hunting as part of closing the session  \n  in ceph_monc_stop()  \n- bail from delayed_work() if monc->cur_mon is cleared, similar to how  \n  it's done in mon_fault() and finish_hunting() (based on monc->hunting)  \n- call cancel_delayed_work_sync() after the session is closed \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"07 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-07T18:38:55.000000Z"}