<?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>Fri, 08 May 2026 13:06:30 +0000</lastBuildDate>
    <item>
      <title>a695b7d1-7241-47b5-9da7-b4d49f1271cd</title>
      <link>https://vulnerability.circl.lu/sighting/a695b7d1-7241-47b5-9da7-b4d49f1271cd/export</link>
      <description>{"uuid": "a695b7d1-7241-47b5-9da7-b4d49f1271cd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21723", "type": "seen", "source": "https://t.me/cvedetector/18993", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21723 - Linux Kernel mpi3mr NULL Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21723 \nPublished : Feb. 27, 2025, 2:15 a.m. | 50\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nscsi: mpi3mr: Fix possible crash when setting up bsg fails  \n  \nIf bsg_setup_queue() fails, the bsg_queue is assigned a non-NULL value.  \nConsequently, in mpi3mr_bsg_exit(), the condition \"if(!mrioc-&amp;gt;bsg_queue)\"  \nwill not be satisfied, preventing execution from entering  \nbsg_remove_queue(), which could lead to the following crash:  \n  \nBUG: kernel NULL pointer dereference, address: 000000000000041c  \nCall Trace:  \n    \n  mpi3mr_bsg_exit+0x1f/0x50 [mpi3mr]  \n  mpi3mr_remove+0x6f/0x340 [mpi3mr]  \n  pci_device_remove+0x3f/0xb0  \n  device_release_driver_internal+0x19d/0x220  \n  unbind_store+0xa4/0xb0  \n  kernfs_fop_write_iter+0x11f/0x200  \n  vfs_write+0x1fc/0x3e0  \n  ksys_write+0x67/0xe0  \n  do_syscall_64+0x38/0x80  \n  entry_SYSCALL_64_after_hwframe+0x78/0xe2 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-27T04:30:31.000000Z"}</description>
      <content:encoded>{"uuid": "a695b7d1-7241-47b5-9da7-b4d49f1271cd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21723", "type": "seen", "source": "https://t.me/cvedetector/18993", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21723 - Linux Kernel mpi3mr NULL Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21723 \nPublished : Feb. 27, 2025, 2:15 a.m. | 50\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nscsi: mpi3mr: Fix possible crash when setting up bsg fails  \n  \nIf bsg_setup_queue() fails, the bsg_queue is assigned a non-NULL value.  \nConsequently, in mpi3mr_bsg_exit(), the condition \"if(!mrioc-&amp;gt;bsg_queue)\"  \nwill not be satisfied, preventing execution from entering  \nbsg_remove_queue(), which could lead to the following crash:  \n  \nBUG: kernel NULL pointer dereference, address: 000000000000041c  \nCall Trace:  \n    \n  mpi3mr_bsg_exit+0x1f/0x50 [mpi3mr]  \n  mpi3mr_remove+0x6f/0x340 [mpi3mr]  \n  pci_device_remove+0x3f/0xb0  \n  device_release_driver_internal+0x19d/0x220  \n  unbind_store+0xa4/0xb0  \n  kernfs_fop_write_iter+0x11f/0x200  \n  vfs_write+0x1fc/0x3e0  \n  ksys_write+0x67/0xe0  \n  do_syscall_64+0x38/0x80  \n  entry_SYSCALL_64_after_hwframe+0x78/0xe2 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-27T04:30:31.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/a695b7d1-7241-47b5-9da7-b4d49f1271cd/export</guid>
      <pubDate>Thu, 27 Feb 2025 04:30:31 +0000</pubDate>
    </item>
    <item>
      <title>1a4ba014-fe96-49cc-a7ed-e600f65e9bf6</title>
      <link>https://vulnerability.circl.lu/sighting/1a4ba014-fe96-49cc-a7ed-e600f65e9bf6/export</link>
      <description>{"uuid": "1a4ba014-fe96-49cc-a7ed-e600f65e9bf6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-21723", "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": "1a4ba014-fe96-49cc-a7ed-e600f65e9bf6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-21723", "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/1a4ba014-fe96-49cc-a7ed-e600f65e9bf6/export</guid>
      <pubDate>Thu, 19 Mar 2026 00:00:00 +0000</pubDate>
    </item>
  </channel>
</rss>
