https://vulnerability.circl.lu/sightings/feed 2026-05-11T00:21:14.484808+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/bd926e06-3fb6-4d9e-85fb-55ede4862ce5/export 2026-05-11T00:21:14.893858+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "bd926e06-3fb6-4d9e-85fb-55ede4862ce5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-53075", "type": "seen", "source": "https://t.me/cvedetector/11476", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-53075 - \"RISC-V Linux Kernel CPU Node Reference Count Vulnerability\"\", \n \"Content\": \"CVE ID : CVE-2024-53075 \nPublished : Nov. 19, 2024, 6:15 p.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nriscv: Prevent a bad reference count on CPU nodes \n \nWhen populating cache leaves we previously fetched the CPU device node \nat the very beginning. But when ACPI is enabled we go through a \nspecific branch which returns early and does not call 'of_node_put' for \nthe node that was acquired. \n \nSince we are not using a CPU device node for the ACPI code anyways, we \ncan simply move the initialization of it just passed the ACPI block, and \nwe are guaranteed to have an 'of_node_put' call for the acquired node. \nThis prevents a bad reference count of the CPU device node. \n \nMoreover, the previous function did not check for errors when acquiring \nthe device node, so a return -ENOENT has been added for that case. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"19 Nov 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-19T20:09:33.000000Z"} 2024-11-19T20:09:33+00:00