https://vulnerability.circl.lu/sightings/feed 2026-05-05T10:33:27.789426+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/b5c3df03-fb08-484b-8b37-6f0093704539/export 2026-05-05T10:33:28.173455+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "b5c3df03-fb08-484b-8b37-6f0093704539", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53003", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/9362", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2023-53003\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nEDAC/qcom: Do not pass llcc_driv_data as edac_device_ctl_info's pvt_info\n\nThe memory for llcc_driv_data is allocated by the LLCC driver. But when\nit is passed as the private driver info to the EDAC core, it will get freed\nduring the qcom_edac driver release. So when the qcom_edac driver gets probed\nagain, it will try to use the freed data leading to the use-after-free bug.\n\nHence, do not pass llcc_driv_data as pvt_info but rather reference it\nusing the platform_data pointer in the qcom_edac driver.\n\ud83d\udccf Published: 2025-03-27T16:43:35.155Z\n\ud83d\udccf Modified: 2025-03-28T15:21:57.079Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/66e10d5f399629ef7877304d9ba2b35d0474e7eb\n2. https://git.kernel.org/stable/c/76d9ebb7f0bc10fbc78b6d576751552edf743968\n3. https://git.kernel.org/stable/c/bff5243bd32661cf9ce66f6d9210fc8f89bda145\n4. https://git.kernel.org/stable/c/6f0351d0c311951b8b3064db91e61841e85b2b96\n5. https://git.kernel.org/stable/c/977c6ba624f24ae20cf0faee871257a39348d4a9", "creation_timestamp": "2025-03-28T15:28:31.000000Z"} 2025-03-28T15:28:31+00:00