https://vulnerability.circl.lu/sightings/feed 2026-05-06T11:22:02.785741+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/323ce1c8-a5dd-4805-82b0-1358dd046ddc/export 2026-05-06T11:22:03.111206+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "323ce1c8-a5dd-4805-82b0-1358dd046ddc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-44955", "type": "seen", "source": "https://t.me/cvedetector/4849", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-44955 - AMD Display Null Pointer Dereference Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-44955 \nPublished : Sept. 4, 2024, 7:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \ndrm/amd/display: Don't refer to dc_sink in is_dsc_need_re_compute \n \n[Why] \nWhen unplug one of monitors connected after mst hub, encounter null pointer dereference. \n \nIt's due to dc_sink get released immediately in early_unregister() or detect_ctx(). When \ncommit new state which directly referring to info stored in dc_sink will cause null pointer \ndereference. \n \n[how] \nRemove redundant checking condition. Relevant condition should already be covered by checking \nif dsc_aux is null or not. Also reset dsc_aux to NULL when the connector is disconnected. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"04 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-04T21:57:05.000000Z"} 2024-09-04T21:57:05+00:00