https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Wed, 27 May 2026 18:23:04 +0000 https://vulnerability.circl.lu/sighting/8e7f5716-d639-4b01-a286-4b5612b8907e/export {"uuid": "8e7f5716-d639-4b01-a286-4b5612b8907e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-44931", "type": "seen", "source": "https://t.me/cvedetector/4122", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-44931 - Linux Kernel GPIO Spectre Information Leak\", \n \"Content\": \"CVE ID : CVE-2024-44931 \nPublished : Aug. 26, 2024, 11:15 a.m. | 21\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \ngpio: prevent potential speculation leaks in gpio_device_get_desc() \n \nUserspace may trigger a speculative read of an address outside the gpio \ndescriptor array. \nUsers can do that by calling gpio_ioctl() with an offset out of range. \nOffset is copied from user and then used as an array index to get \nthe gpio descriptor without sanitization in gpio_device_get_desc(). \n \nThis change ensures that the offset is sanitized by using \narray_index_nospec() to mitigate any possibility of speculative \ninformation leaks. \n \nThis bug was discovered and resolved using Coverity Static Analysis \nSecurity Testing (SAST) by Synopsys, Inc. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"26 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-26T13:42:51.000000Z"} {"uuid": "8e7f5716-d639-4b01-a286-4b5612b8907e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-44931", "type": "seen", "source": "https://t.me/cvedetector/4122", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-44931 - Linux Kernel GPIO Spectre Information Leak\", \n \"Content\": \"CVE ID : CVE-2024-44931 \nPublished : Aug. 26, 2024, 11:15 a.m. | 21\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \ngpio: prevent potential speculation leaks in gpio_device_get_desc() \n \nUserspace may trigger a speculative read of an address outside the gpio \ndescriptor array. \nUsers can do that by calling gpio_ioctl() with an offset out of range. \nOffset is copied from user and then used as an array index to get \nthe gpio descriptor without sanitization in gpio_device_get_desc(). \n \nThis change ensures that the offset is sanitized by using \narray_index_nospec() to mitigate any possibility of speculative \ninformation leaks. \n \nThis bug was discovered and resolved using Coverity Static Analysis \nSecurity Testing (SAST) by Synopsys, Inc. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"26 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-26T13:42:51.000000Z"} https://vulnerability.circl.lu/sighting/8e7f5716-d639-4b01-a286-4b5612b8907e/export Mon, 26 Aug 2024 13:42:51 +0000