<?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, 27 May 2026 18:28:02 +0000</lastBuildDate>
    <item>
      <title>7b29a9ba-e376-424e-ad68-4a2e0590af1b</title>
      <link>https://vulnerability.circl.lu/sighting/7b29a9ba-e376-424e-ad68-4a2e0590af1b/export</link>
      <description>{"uuid": "7b29a9ba-e376-424e-ad68-4a2e0590af1b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-41079", "type": "seen", "source": "https://t.me/cvedetector/1855", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-41079 - NVIDIA NVMe Target Memory Disclosure\", \n  \"Content\": \"CVE ID : CVE-2024-41079 \nPublished : July 29, 2024, 3:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnvmet: always initialize cqe.result  \n  \nThe spec doesn't mandate that the first two double words (aka results)  \nfor the command queue entry need to be set to 0 when they are not  \nused (not specified). Though, the target implemention returns 0 for TCP  \nand FC but not for RDMA.  \n  \nLet's make RDMA behave the same and thus explicitly initializing the  \nresult field. This prevents leaking any data from the stack. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-29T17:57:56.000000Z"}</description>
      <content:encoded>{"uuid": "7b29a9ba-e376-424e-ad68-4a2e0590af1b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-41079", "type": "seen", "source": "https://t.me/cvedetector/1855", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-41079 - NVIDIA NVMe Target Memory Disclosure\", \n  \"Content\": \"CVE ID : CVE-2024-41079 \nPublished : July 29, 2024, 3:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnvmet: always initialize cqe.result  \n  \nThe spec doesn't mandate that the first two double words (aka results)  \nfor the command queue entry need to be set to 0 when they are not  \nused (not specified). Though, the target implemention returns 0 for TCP  \nand FC but not for RDMA.  \n  \nLet's make RDMA behave the same and thus explicitly initializing the  \nresult field. This prevents leaking any data from the stack. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-29T17:57:56.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/7b29a9ba-e376-424e-ad68-4a2e0590af1b/export</guid>
      <pubDate>Mon, 29 Jul 2024 17:57:56 +0000</pubDate>
    </item>
    <item>
      <title>4a4c921c-d9e1-438c-9991-b956c64ef8bf</title>
      <link>https://vulnerability.circl.lu/sighting/4a4c921c-d9e1-438c-9991-b956c64ef8bf/export</link>
      <description>{"uuid": "4a4c921c-d9e1-438c-9991-b956c64ef8bf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-41079", "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": "4a4c921c-d9e1-438c-9991-b956c64ef8bf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-41079", "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/4a4c921c-d9e1-438c-9991-b956c64ef8bf/export</guid>
      <pubDate>Wed, 03 Dec 2025 14:14:49 +0000</pubDate>
    </item>
    <item>
      <title>a49d53d3-0b0a-454b-9f4b-e398af68f7a8</title>
      <link>https://vulnerability.circl.lu/sighting/a49d53d3-0b0a-454b-9f4b-e398af68f7a8/export</link>
      <description>{"uuid": "a49d53d3-0b0a-454b-9f4b-e398af68f7a8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-41079", "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": "a49d53d3-0b0a-454b-9f4b-e398af68f7a8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-41079", "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/a49d53d3-0b0a-454b-9f4b-e398af68f7a8/export</guid>
      <pubDate>Thu, 19 Mar 2026 00:00:00 +0000</pubDate>
    </item>
  </channel>
</rss>
