<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent sightings.</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent sightings.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 06 May 2026 18:42:44 +0000</lastBuildDate>
    <item>
      <title>323ce1c8-a5dd-4805-82b0-1358dd046ddc</title>
      <link>https://vulnerability.circl.lu/sighting/323ce1c8-a5dd-4805-82b0-1358dd046ddc/export</link>
      <description>{"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"}</description>
      <content:encoded>{"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"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/323ce1c8-a5dd-4805-82b0-1358dd046ddc/export</guid>
      <pubDate>Wed, 04 Sep 2024 21:57:05 +0000</pubDate>
    </item>
  </channel>
</rss>
