https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Thu, 28 May 2026 19:50:44 +0000 https://vulnerability.circl.lu/sighting/e14a7ca0-dfc6-47fa-940e-e1f9a6005416/export {"uuid": "e14a7ca0-dfc6-47fa-940e-e1f9a6005416", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-40945", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/4898", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-40945\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\niommu: Return right value in iommu_sva_bind_device()\n\niommu_sva_bind_device() should return either a sva bond handle or an\nERR_PTR value in error cases. Existing drivers (idxd and uacce) only\ncheck the return value with IS_ERR(). This could potentially lead to\na kernel NULL pointer dereference issue if the function returns NULL\ninstead of an error pointer.\n\nIn reality, this doesn't cause any problems because iommu_sva_bind_device()\nonly returns NULL when the kernel is not configured with CONFIG_IOMMU_SVA.\nIn this case, iommu_dev_enable_feature(dev, IOMMU_DEV_FEAT_SVA) will\nreturn an error, and the device drivers won't call iommu_sva_bind_device()\nat all.\n\ud83d\udccf Published: 2024-07-12T12:25:19.164Z\n\ud83d\udccf Modified: 2025-02-21T13:45:06.636Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/700f564758882db7c039dfba9443fe762561a3f8\n2. https://git.kernel.org/stable/c/cf34f8f66982a36e5cba0d05781b21ec9606b91e\n3. https://git.kernel.org/stable/c/2973b8e7d127754de9013177c41c0b5547406998\n4. https://git.kernel.org/stable/c/6325eab6c108fed27f60ff51852e3eac0ba23f3f\n5. https://git.kernel.org/stable/c/7388ae6f26c0ba95f70cc96bf9c5d5cb06c908b6\n6. https://git.kernel.org/stable/c/61a96da9649a6b6a1a5d5bde9374b045fdb5c12e\n7. https://git.kernel.org/stable/c/89e8a2366e3bce584b6c01549d5019c5cda1205e", "creation_timestamp": "2025-02-21T14:18:36.000000Z"} {"uuid": "e14a7ca0-dfc6-47fa-940e-e1f9a6005416", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-40945", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/4898", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-40945\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\niommu: Return right value in iommu_sva_bind_device()\n\niommu_sva_bind_device() should return either a sva bond handle or an\nERR_PTR value in error cases. Existing drivers (idxd and uacce) only\ncheck the return value with IS_ERR(). This could potentially lead to\na kernel NULL pointer dereference issue if the function returns NULL\ninstead of an error pointer.\n\nIn reality, this doesn't cause any problems because iommu_sva_bind_device()\nonly returns NULL when the kernel is not configured with CONFIG_IOMMU_SVA.\nIn this case, iommu_dev_enable_feature(dev, IOMMU_DEV_FEAT_SVA) will\nreturn an error, and the device drivers won't call iommu_sva_bind_device()\nat all.\n\ud83d\udccf Published: 2024-07-12T12:25:19.164Z\n\ud83d\udccf Modified: 2025-02-21T13:45:06.636Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/700f564758882db7c039dfba9443fe762561a3f8\n2. https://git.kernel.org/stable/c/cf34f8f66982a36e5cba0d05781b21ec9606b91e\n3. https://git.kernel.org/stable/c/2973b8e7d127754de9013177c41c0b5547406998\n4. https://git.kernel.org/stable/c/6325eab6c108fed27f60ff51852e3eac0ba23f3f\n5. https://git.kernel.org/stable/c/7388ae6f26c0ba95f70cc96bf9c5d5cb06c908b6\n6. https://git.kernel.org/stable/c/61a96da9649a6b6a1a5d5bde9374b045fdb5c12e\n7. https://git.kernel.org/stable/c/89e8a2366e3bce584b6c01549d5019c5cda1205e", "creation_timestamp": "2025-02-21T14:18:36.000000Z"} https://vulnerability.circl.lu/sighting/e14a7ca0-dfc6-47fa-940e-e1f9a6005416/export Fri, 21 Feb 2025 14:18:36 +0000 https://vulnerability.circl.lu/sighting/2dd67071-7788-431a-aaad-cfb5b08383fc/export {"uuid": "2dd67071-7788-431a-aaad-cfb5b08383fc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-40945", "type": "seen", "source": "Telegram/ORzEuWXvIyoumP8DzeA1wY4TER2LyW7K1HGuVplZfB8dwvcy", "content": "", "creation_timestamp": "2025-02-21T22:10:23.000000Z"} {"uuid": "2dd67071-7788-431a-aaad-cfb5b08383fc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-40945", "type": "seen", "source": "Telegram/ORzEuWXvIyoumP8DzeA1wY4TER2LyW7K1HGuVplZfB8dwvcy", "content": "", "creation_timestamp": "2025-02-21T22:10:23.000000Z"} https://vulnerability.circl.lu/sighting/2dd67071-7788-431a-aaad-cfb5b08383fc/export Fri, 21 Feb 2025 22:10:23 +0000 https://vulnerability.circl.lu/sighting/8fd14906-d281-4db0-9b27-871fe2b7b204/export {"uuid": "8fd14906-d281-4db0-9b27-871fe2b7b204", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-40945", "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": "8fd14906-d281-4db0-9b27-871fe2b7b204", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-40945", "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/8fd14906-d281-4db0-9b27-871fe2b7b204/export Thu, 14 Aug 2025 10:00:00 +0000