<?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>Sat, 09 May 2026 20:46:12 +0000</lastBuildDate>
    <item>
      <title>ffd9ca11-9234-44be-8d47-ec89441e8aca</title>
      <link>https://vulnerability.circl.lu/sighting/ffd9ca11-9234-44be-8d47-ec89441e8aca/export</link>
      <description>{"uuid": "ffd9ca11-9234-44be-8d47-ec89441e8aca", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50003", "type": "seen", "source": "https://t.me/cvedetector/8540", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50003 - \"AMD Display Thunderbolt Suspend Hang\"\", \n  \"Content\": \"CVE ID : CVE-2024-50003 \nPublished : Oct. 21, 2024, 7:15 p.m. | 34\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/amd/display: Fix system hang while resume with TBT monitor  \n  \n[Why]  \nConnected with a Thunderbolt monitor and do the suspend and the system  \nmay hang while resume.  \n  \nThe TBT monitor HPD will be triggered during the resume procedure  \nand call the drm_client_modeset_probe() while  \nstruct drm_connector connector-&amp;gt;dev-&amp;gt;master is NULL.  \n  \nIt will mess up the pipe topology after resume.  \n  \n[How]  \nSkip the TBT monitor HPD during the resume procedure because we  \ncurrently will probe the connectors after resume by default.  \n  \n(cherry picked from commit 453f86a26945207a16b8f66aaed5962dc2b95b85) \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-21T21:52:45.000000Z"}</description>
      <content:encoded>{"uuid": "ffd9ca11-9234-44be-8d47-ec89441e8aca", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50003", "type": "seen", "source": "https://t.me/cvedetector/8540", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50003 - \"AMD Display Thunderbolt Suspend Hang\"\", \n  \"Content\": \"CVE ID : CVE-2024-50003 \nPublished : Oct. 21, 2024, 7:15 p.m. | 34\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/amd/display: Fix system hang while resume with TBT monitor  \n  \n[Why]  \nConnected with a Thunderbolt monitor and do the suspend and the system  \nmay hang while resume.  \n  \nThe TBT monitor HPD will be triggered during the resume procedure  \nand call the drm_client_modeset_probe() while  \nstruct drm_connector connector-&amp;gt;dev-&amp;gt;master is NULL.  \n  \nIt will mess up the pipe topology after resume.  \n  \n[How]  \nSkip the TBT monitor HPD during the resume procedure because we  \ncurrently will probe the connectors after resume by default.  \n  \n(cherry picked from commit 453f86a26945207a16b8f66aaed5962dc2b95b85) \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-21T21:52:45.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/ffd9ca11-9234-44be-8d47-ec89441e8aca/export</guid>
      <pubDate>Mon, 21 Oct 2024 21:52:45 +0000</pubDate>
    </item>
    <item>
      <title>a8d2fc50-8a8a-4a05-b5f5-2f80f235179f</title>
      <link>https://vulnerability.circl.lu/sighting/a8d2fc50-8a8a-4a05-b5f5-2f80f235179f/export</link>
      <description>{"uuid": "a8d2fc50-8a8a-4a05-b5f5-2f80f235179f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-50003", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}</description>
      <content:encoded>{"uuid": "a8d2fc50-8a8a-4a05-b5f5-2f80f235179f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-50003", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/a8d2fc50-8a8a-4a05-b5f5-2f80f235179f/export</guid>
      <pubDate>Wed, 03 Dec 2025 14:14:49 +0000</pubDate>
    </item>
  </channel>
</rss>
