https://vulnerability.circl.lu/sightings/feed 2026-05-27T16:28:50.105458+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/8f59bc86-e40b-4151-9f4d-3387b47daadf/export 2026-05-27T16:28:50.479921+00:00 Automation user https://vulnerability.circl.lu/user/automation {"uuid": "8f59bc86-e40b-4151-9f4d-3387b47daadf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-39491", "type": "seen", "source": "https://t.me/cvedetector/525", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-39491 - In the Linux kernel, the following vulnerability h\", \n \"Content\": \"CVE ID : CVE-2024-39491 \nPublished : July 10, 2024, 8:15 a.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nALSA: hda: cs35l56: Fix lifetime of cs_dsp instance \n \nThe cs_dsp instance is initialized in the driver probe() so it \nshould be freed in the driver remove(). Also fix a missing call \nto cs_dsp_remove() in the error path of cs35l56_hda_common_probe(). \n \nThe call to cs_dsp_remove() was being done in the component unbind \ncallback cs35l56_hda_unbind(). This meant that if the driver was \nunbound and then re-bound it would be using an uninitialized cs_dsp \ninstance. \n \nIt is best to initialize the cs_dsp instance in probe() so that it \ncan return an error if it fails. The component binding API doesn't \nhave any error handling so there's no way to handle a failure if \ncs_dsp was initialized in the bind. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"10 Jul 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-10T10:54:43.000000Z"} 2024-07-10T10:54:43+00:00