{"uuid": "e4ccf72b-9372-4ee6-9795-3dfcae566f79", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-47660", "type": "seen", "source": "https://t.me/cvedetector/7470", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-47660 - \"Linux filesystem Denial of Service (DoS) Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-47660 \nPublished : Oct. 9, 2024, 2:15 p.m. | 38\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nfsnotify: clear PARENT_WATCHED flags lazily  \n  \nIn some setups directories can have many (usually negative) dentries.  \nHence __fsnotify_update_child_dentry_flags() function can take a  \nsignificant amount of time. Since the bulk of this function happens  \nunder inode->i_lock this causes a significant contention on the lock  \nwhen we remove the watch from the directory as the  \n__fsnotify_update_child_dentry_flags() call from fsnotify_recalc_mask()  \nraces with __fsnotify_update_child_dentry_flags() calls from  \n__fsnotify_parent() happening on children. This can lead upto softlockup  \nreports reported by users.  \n  \nFix the problem by calling fsnotify_update_children_dentry_flags() to  \nset PARENT_WATCHED flags only when parent starts watching children.  \n  \nWhen parent stops watching children, clear false positive PARENT_WATCHED  \nflags lazily in __fsnotify_parent() for each accessed child. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-09T17:19:15.000000Z"}