https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Wed, 27 May 2026 21:49:16 +0000 https://vulnerability.circl.lu/sighting/e4ccf72b-9372-4ee6-9795-3dfcae566f79/export {"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"} {"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"} https://vulnerability.circl.lu/sighting/e4ccf72b-9372-4ee6-9795-3dfcae566f79/export Wed, 09 Oct 2024 17:19:15 +0000 https://vulnerability.circl.lu/sighting/432a0b11-d09f-41fa-9b54-ce37c4b9de85/export {"uuid": "432a0b11-d09f-41fa-9b54-ce37c4b9de85", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-47660", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-07", "content": "", "creation_timestamp": "2025-08-14T10:00:00.000000Z"} {"uuid": "432a0b11-d09f-41fa-9b54-ce37c4b9de85", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-47660", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-07", "content": "", "creation_timestamp": "2025-08-14T10:00:00.000000Z"} https://vulnerability.circl.lu/sighting/432a0b11-d09f-41fa-9b54-ce37c4b9de85/export Thu, 14 Aug 2025 10:00:00 +0000 https://vulnerability.circl.lu/sighting/70d3b0c0-f303-47cf-bcad-54791c645e6a/export {"uuid": "70d3b0c0-f303-47cf-bcad-54791c645e6a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-47660", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} {"uuid": "70d3b0c0-f303-47cf-bcad-54791c645e6a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-47660", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} https://vulnerability.circl.lu/sighting/70d3b0c0-f303-47cf-bcad-54791c645e6a/export Wed, 03 Dec 2025 14:14:49 +0000