https://db.gcve.eu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Sat, 30 May 2026 14:22:16 +0000 https://db.gcve.eu/sighting/ff5c0017-7862-4ff5-8706-01466e8111ca/export {"uuid": "ff5c0017-7862-4ff5-8706-01466e8111ca", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57940", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113866341978131633", "content": "", "creation_timestamp": "2025-01-21T12:28:14.201169Z"} {"uuid": "ff5c0017-7862-4ff5-8706-01466e8111ca", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57940", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113866341978131633", "content": "", "creation_timestamp": "2025-01-21T12:28:14.201169Z"} https://db.gcve.eu/sighting/ff5c0017-7862-4ff5-8706-01466e8111ca/export Tue, 21 Jan 2025 12:28:14 +0000 https://db.gcve.eu/sighting/94bafdba-74e2-4ec9-9fb5-0be360d5fea1/export {"uuid": "94bafdba-74e2-4ec9-9fb5-0be360d5fea1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57940", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lgawqeryja2f", "content": "", "creation_timestamp": "2025-01-21T13:15:45.343808Z"} {"uuid": "94bafdba-74e2-4ec9-9fb5-0be360d5fea1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57940", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lgawqeryja2f", "content": "", "creation_timestamp": "2025-01-21T13:15:45.343808Z"} https://db.gcve.eu/sighting/94bafdba-74e2-4ec9-9fb5-0be360d5fea1/export Tue, 21 Jan 2025 13:15:45 +0000 https://db.gcve.eu/sighting/05f8e3ce-66a3-4b07-b4b3-2b298e2c341c/export {"uuid": "05f8e3ce-66a3-4b07-b4b3-2b298e2c341c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57940", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lgay2twr752y", "content": "", "creation_timestamp": "2025-01-21T13:39:34.926491Z"} {"uuid": "05f8e3ce-66a3-4b07-b4b3-2b298e2c341c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57940", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lgay2twr752y", "content": "", "creation_timestamp": "2025-01-21T13:39:34.926491Z"} https://db.gcve.eu/sighting/05f8e3ce-66a3-4b07-b4b3-2b298e2c341c/export Tue, 21 Jan 2025 13:39:34 +0000 https://db.gcve.eu/sighting/6c4cfb85-a05a-4d91-a814-bfb0d95359fc/export {"uuid": "6c4cfb85-a05a-4d91-a814-bfb0d95359fc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57940", "type": "seen", "source": "https://t.me/cvedetector/15949", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-57940 - Exfat Infinite Cluster Loop Denial of Service\", \n \"Content\": \"CVE ID : CVE-2024-57940 \nPublished : Jan. 21, 2025, 1:15 p.m. | 42\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nexfat: fix the infinite loop in exfat_readdir() \n \nIf the file system is corrupted so that a cluster is linked to \nitself in the cluster chain, and there is an unused directory \nentry in the cluster, 'dentry' will not be incremented, causing \ncondition 'dentry < max_dentries' unable to prevent an infinite \nloop. \n \nThis infinite loop causes s_lock not to be released, and other \ntasks will hang, such as exfat_sync_fs(). \n \nThis commit stops traversing the cluster chain when there is unused \ndirectory entry in the cluster to avoid this infinite loop. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"21 Jan 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-21T15:17:34.000000Z"} {"uuid": "6c4cfb85-a05a-4d91-a814-bfb0d95359fc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57940", "type": "seen", "source": "https://t.me/cvedetector/15949", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-57940 - Exfat Infinite Cluster Loop Denial of Service\", \n \"Content\": \"CVE ID : CVE-2024-57940 \nPublished : Jan. 21, 2025, 1:15 p.m. | 42\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nexfat: fix the infinite loop in exfat_readdir() \n \nIf the file system is corrupted so that a cluster is linked to \nitself in the cluster chain, and there is an unused directory \nentry in the cluster, 'dentry' will not be incremented, causing \ncondition 'dentry < max_dentries' unable to prevent an infinite \nloop. \n \nThis infinite loop causes s_lock not to be released, and other \ntasks will hang, such as exfat_sync_fs(). \n \nThis commit stops traversing the cluster chain when there is unused \ndirectory entry in the cluster to avoid this infinite loop. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"21 Jan 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-21T15:17:34.000000Z"} https://db.gcve.eu/sighting/6c4cfb85-a05a-4d91-a814-bfb0d95359fc/export Tue, 21 Jan 2025 15:17:34 +0000