{"uuid": "d2325358-84d9-45ee-aa3b-a41bd9387c9c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-50006", "type": "seen", "source": "https://t.me/cvedetector/8541", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50006 - Linux Kernel EXT4 Data Semaphores Deadlock\", \n  \"Content\": \"CVE ID : CVE-2024-50006 \nPublished : Oct. 21, 2024, 7:15 p.m. | 34\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \next4: fix i_data_sem unlock order in ext4_ind_migrate()  \n  \nFuzzing reports a possible deadlock in jbd2_log_wait_commit.  \n  \nThis issue is triggered when an EXT4_IOC_MIGRATE ioctl is set to require  \nsynchronous updates because the file descriptor is opened with O_SYNC.  \nThis can lead to the jbd2_journal_stop() function calling  \njbd2_might_wait_for_commit(), potentially causing a deadlock if the  \nEXT4_IOC_MIGRATE call races with a write(2) system call.  \n  \nThis problem only arises when CONFIG_PROVE_LOCKING is enabled. In this  \ncase, the jbd2_might_wait_for_commit macro locks jbd2_handle in the  \njbd2_journal_stop function while i_data_sem is locked. This triggers  \nlockdep because the jbd2_journal_start function might also lock the same  \njbd2_handle simultaneously.  \n  \nFound by Linux Verification Center (linuxtesting.org) with syzkaller.  \n  \nRule: add \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-21T21:52:49.000000Z"}