<?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>Thu, 01 Oct 2026 11:34:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50506 — drbd: only clone bio if we have a backing device</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-50506</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;drbd: only clone bio if we have a backing device&lt;/p&gt;
&lt;p&gt;Commit c347a787e34cb (drbd: set -&amp;gt;bi_bdev in drbd_req_new) moved a
bio_set_dev call (which has since been removed) to &amp;#34;earlier&amp;#34;, from
drbd_request_prepare to drbd_req_new.&lt;/p&gt;
&lt;p&gt;The problem is that this accesses device-&amp;gt;ldev-&amp;gt;backing_bdev, which is
not NULL-checked at this point. When we don&amp;#39;t have an ldev (i.e. when
the DRBD device is diskless), this leads to a null pointer deref.&lt;/p&gt;
&lt;p&gt;So, only allocate the private_bio if we actually have a disk. This is
also a small optimization, since we don&amp;#39;t clone the bio to only to
immediately free it again in the diskless case.&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;drbd: only clone bio if we have a backing device&lt;/p&gt;
&lt;p&gt;Commit c347a787e34cb (drbd: set -&amp;gt;bi_bdev in drbd_req_new) moved a
bio_set_dev call (which has since been removed) to &amp;#34;earlier&amp;#34;, from
drbd_request_prepare to drbd_req_new.&lt;/p&gt;
&lt;p&gt;The problem is that this accesses device-&amp;gt;ldev-&amp;gt;backing_bdev, which is
not NULL-checked at this point. When we don&amp;#39;t have an ldev (i.e. when
the DRBD device is diskless), this leads to a null pointer deref.&lt;/p&gt;
&lt;p&gt;So, only allocate the private_bio if we actually have a disk. This is
also a small optimization, since we don&amp;#39;t clone the bio to only to
immediately free it again in the diskless case.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-50506</guid>
    </item>
  </channel>
</rss>
