<?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 entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 20:04:28 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-02517</title>
      <link>https://vulnerability.circl.lu/vuln/bdu:2026-02517</link>
      <description>bdu:2026-02517</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bdu:2026-02517</guid>
    </item>
    <item>
      <title>CVE-2023-53373 — crypto: seqiv - Handle EBUSY correctly</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53373</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;crypto: seqiv - Handle EBUSY correctly&lt;/p&gt;
&lt;p&gt;As it is seqiv only handles the special return value of EINPROGERSS,
which means that in all other cases it will free data related to the
request.&lt;/p&gt;
&lt;p&gt;However, as the caller of seqiv may specify MAY_BACKLOG, we also need
to expect EBUSY and treat it in the same way.  Otherwise backlogged
requests will trigger a use-after-free.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;crypto: seqiv - Handle EBUSY correctly&lt;/p&gt;
&lt;p&gt;As it is seqiv only handles the special return value of EINPROGERSS,
which means that in all other cases it will free data related to the
request.&lt;/p&gt;
&lt;p&gt;However, as the caller of seqiv may specify MAY_BACKLOG, we also need
to expect EBUSY and treat it in the same way.  Otherwise backlogged
requests will trigger a use-after-free.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53373</guid>
    </item>
  </channel>
</rss>
