https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Sat, 09 May 2026 05:43:54 +0000 https://vulnerability.circl.lu/sighting/a70bd397-a2cf-4092-86f3-403b665baba4/export {"uuid": "a70bd397-a2cf-4092-86f3-403b665baba4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-58092", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12006", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-58092\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: fix legacy client tracking initialization\n\nGet rid of the nfsd4_legacy_tracking_ops->init() call in\ncheck_for_legacy_methods(). That will be handled in the caller\n(nfsd4_client_tracking_init()). Otherwise, we'll wind up calling\nnfsd4_legacy_tracking_ops->init() twice, and the second time we'll\ntrigger the BUG_ON() in nfsd4_init_recdir().\n\ud83d\udccf Published: 2025-04-16T10:24:53.056Z\n\ud83d\udccf Modified: 2025-04-16T10:24:53.056Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/95407304253a4bf03494d921c6913e220c26cc63\n2. https://git.kernel.org/stable/c/cdd66082b227eb695cbf54b7c121ea032e869981\n3. https://git.kernel.org/stable/c/de71d4e211eddb670b285a0ea477a299601ce1ca", "creation_timestamp": "2025-04-16T10:55:49.000000Z"} {"uuid": "a70bd397-a2cf-4092-86f3-403b665baba4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-58092", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12006", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-58092\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: fix legacy client tracking initialization\n\nGet rid of the nfsd4_legacy_tracking_ops->init() call in\ncheck_for_legacy_methods(). That will be handled in the caller\n(nfsd4_client_tracking_init()). Otherwise, we'll wind up calling\nnfsd4_legacy_tracking_ops->init() twice, and the second time we'll\ntrigger the BUG_ON() in nfsd4_init_recdir().\n\ud83d\udccf Published: 2025-04-16T10:24:53.056Z\n\ud83d\udccf Modified: 2025-04-16T10:24:53.056Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/95407304253a4bf03494d921c6913e220c26cc63\n2. https://git.kernel.org/stable/c/cdd66082b227eb695cbf54b7c121ea032e869981\n3. https://git.kernel.org/stable/c/de71d4e211eddb670b285a0ea477a299601ce1ca", "creation_timestamp": "2025-04-16T10:55:49.000000Z"} https://vulnerability.circl.lu/sighting/a70bd397-a2cf-4092-86f3-403b665baba4/export Wed, 16 Apr 2025 10:55:49 +0000 https://vulnerability.circl.lu/sighting/e9e3c0c3-86a5-46f8-af42-48d0ecd72a23/export {"uuid": "e9e3c0c3-86a5-46f8-af42-48d0ecd72a23", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-58092", "type": "seen", "source": "https://t.me/cvedetector/23070", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-58092 - Linux Kernel NFSd Double Initialization Double-Free Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-58092 \nPublished : April 16, 2025, 11:15 a.m. | 14\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nnfsd: fix legacy client tracking initialization \n \nGet rid of the nfsd4_legacy_tracking_ops->init() call in \ncheck_for_legacy_methods(). That will be handled in the caller \n(nfsd4_client_tracking_init()). Otherwise, we'll wind up calling \nnfsd4_legacy_tracking_ops->init() twice, and the second time we'll \ntrigger the BUG_ON() in nfsd4_init_recdir(). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"16 Apr 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-16T13:31:21.000000Z"} {"uuid": "e9e3c0c3-86a5-46f8-af42-48d0ecd72a23", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-58092", "type": "seen", "source": "https://t.me/cvedetector/23070", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-58092 - Linux Kernel NFSd Double Initialization Double-Free Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-58092 \nPublished : April 16, 2025, 11:15 a.m. | 14\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nnfsd: fix legacy client tracking initialization \n \nGet rid of the nfsd4_legacy_tracking_ops->init() call in \ncheck_for_legacy_methods(). That will be handled in the caller \n(nfsd4_client_tracking_init()). Otherwise, we'll wind up calling \nnfsd4_legacy_tracking_ops->init() twice, and the second time we'll \ntrigger the BUG_ON() in nfsd4_init_recdir(). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"16 Apr 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-16T13:31:21.000000Z"} https://vulnerability.circl.lu/sighting/e9e3c0c3-86a5-46f8-af42-48d0ecd72a23/export Wed, 16 Apr 2025 13:31:21 +0000