<?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>Thu, 04 Jun 2026 00:34:08 +0000</lastBuildDate>
    <item>
      <title>66094091-b9c7-4ce5-b748-2e5ef7e6d012</title>
      <link>https://vulnerability.circl.lu/sighting/66094091-b9c7-4ce5-b748-2e5ef7e6d012/export</link>
      <description>{"uuid": "66094091-b9c7-4ce5-b748-2e5ef7e6d012", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-50016", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/18854", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2022-50016\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: SOF: Intel: cnl: Do not process IPC reply before firmware boot\n\nIt is not yet clear, but it is possible to create a firmware so broken\nthat it will send a reply message before a FW_READY message (it is not\nyet clear if FW_READY will arrive later).\nSince the reply_data is allocated only after the FW_READY message, this\nwill lead to a NULL pointer dereference if not filtered out.\n\nThe issue was reported with IPC4 firmware but the same condition is present\nfor IPC3.\n\ud83d\udccf Published: 2025-06-18T11:01:20.427Z\n\ud83d\udccf Modified: 2025-06-19T13:10:48.324Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/230f646085d17a008b609eb8fe8befb8811868f0\n2. https://git.kernel.org/stable/c/acacd9eefd0def5a83244d88e5483b5f38ee7287", "creation_timestamp": "2025-06-19T13:39:47.000000Z"}</description>
      <content:encoded>{"uuid": "66094091-b9c7-4ce5-b748-2e5ef7e6d012", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-50016", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/18854", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2022-50016\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: SOF: Intel: cnl: Do not process IPC reply before firmware boot\n\nIt is not yet clear, but it is possible to create a firmware so broken\nthat it will send a reply message before a FW_READY message (it is not\nyet clear if FW_READY will arrive later).\nSince the reply_data is allocated only after the FW_READY message, this\nwill lead to a NULL pointer dereference if not filtered out.\n\nThe issue was reported with IPC4 firmware but the same condition is present\nfor IPC3.\n\ud83d\udccf Published: 2025-06-18T11:01:20.427Z\n\ud83d\udccf Modified: 2025-06-19T13:10:48.324Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/230f646085d17a008b609eb8fe8befb8811868f0\n2. https://git.kernel.org/stable/c/acacd9eefd0def5a83244d88e5483b5f38ee7287", "creation_timestamp": "2025-06-19T13:39:47.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/66094091-b9c7-4ce5-b748-2e5ef7e6d012/export</guid>
      <pubDate>Thu, 19 Jun 2025 13:39:47 +0000</pubDate>
    </item>
    <item>
      <title>14166738-4dd0-450d-8839-e20f7362230b</title>
      <link>https://vulnerability.circl.lu/sighting/14166738-4dd0-450d-8839-e20f7362230b/export</link>
      <description>{"uuid": "14166738-4dd0-450d-8839-e20f7362230b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2022-50016", "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": "14166738-4dd0-450d-8839-e20f7362230b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2022-50016", "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/14166738-4dd0-450d-8839-e20f7362230b/export</guid>
      <pubDate>Wed, 03 Dec 2025 14:14:49 +0000</pubDate>
    </item>
    <item>
      <title>2f4e8e45-e0f9-4830-82fd-acfcf42b484a</title>
      <link>https://vulnerability.circl.lu/sighting/2f4e8e45-e0f9-4830-82fd-acfcf42b484a/export</link>
      <description>{"uuid": "2f4e8e45-e0f9-4830-82fd-acfcf42b484a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2022-50016", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}</description>
      <content:encoded>{"uuid": "2f4e8e45-e0f9-4830-82fd-acfcf42b484a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2022-50016", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/2f4e8e45-e0f9-4830-82fd-acfcf42b484a/export</guid>
      <pubDate>Thu, 19 Mar 2026 00:00:00 +0000</pubDate>
    </item>
  </channel>
</rss>
