https://vulnerability.circl.lu/sightings/feed 2026-05-27T15:24:29.408992+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/cc36fe2c-a3c5-468b-aa20-cd849c7023ea/export 2026-05-27T15:24:29.901043+00:00 Automation user https://vulnerability.circl.lu/user/automation {"uuid": "cc36fe2c-a3c5-468b-aa20-cd849c7023ea", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50064", "type": "seen", "source": "https://t.me/cvedetector/8547", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-50064 - Linux zram Memory Leak\", \n \"Content\": \"CVE ID : CVE-2024-50064 \nPublished : Oct. 21, 2024, 8:15 p.m. | 16\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nzram: free secondary algorithms names \n \nWe need to kfree() secondary algorithms names when reset zram device that \nhad multi-streams, otherwise we leak memory. \n \n[senozhatsky@chromium.org: kfree(NULL) is legal] \n Link: \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"21 Oct 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-21T22:42:55.000000Z"} 2024-10-21T22:42:55+00:00