<?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>Mon, 11 May 2026 06:41:15 +0000</lastBuildDate>
    <item>
      <title>ab92933a-3c72-4106-9556-3a285b16f919</title>
      <link>https://vulnerability.circl.lu/sighting/ab92933a-3c72-4106-9556-3a285b16f919/export</link>
      <description>{"uuid": "ab92933a-3c72-4106-9556-3a285b16f919", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-52895", "type": "seen", "source": "https://t.me/cvedetector/3749", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-52895 - Linux Kernel io_uring Poll Multipurpose Buffer Leak\", \n  \"Content\": \"CVE ID : CVE-2023-52895 \nPublished : Aug. 21, 2024, 7:15 a.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nio_uring/poll: don't reissue in case of poll race on multishot request  \n  \nA previous commit fixed a poll race that can occur, but it's only  \napplicable for multishot requests. For a multishot request, we can safely  \nignore a spurious wakeup, as we never leave the waitqueue to begin with.  \n  \nA blunt reissue of a multishot armed request can cause us to leak a  \nbuffer, if they are ring provided. While this seems like a bug in itself,  \nit's not really defined behavior to reissue a multishot request directly.  \nIt's less efficient to do so as well, and not required to rearm anything  \nlike it is for singleshot poll requests. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-21T09:52:14.000000Z"}</description>
      <content:encoded>{"uuid": "ab92933a-3c72-4106-9556-3a285b16f919", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-52895", "type": "seen", "source": "https://t.me/cvedetector/3749", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-52895 - Linux Kernel io_uring Poll Multipurpose Buffer Leak\", \n  \"Content\": \"CVE ID : CVE-2023-52895 \nPublished : Aug. 21, 2024, 7:15 a.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nio_uring/poll: don't reissue in case of poll race on multishot request  \n  \nA previous commit fixed a poll race that can occur, but it's only  \napplicable for multishot requests. For a multishot request, we can safely  \nignore a spurious wakeup, as we never leave the waitqueue to begin with.  \n  \nA blunt reissue of a multishot armed request can cause us to leak a  \nbuffer, if they are ring provided. While this seems like a bug in itself,  \nit's not really defined behavior to reissue a multishot request directly.  \nIt's less efficient to do so as well, and not required to rearm anything  \nlike it is for singleshot poll requests. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-21T09:52:14.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/ab92933a-3c72-4106-9556-3a285b16f919/export</guid>
      <pubDate>Wed, 21 Aug 2024 09:52:14 +0000</pubDate>
    </item>
  </channel>
</rss>
