<?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>Fri, 02 Oct 2026 19:38:41 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-46294 — dm: fix a buffer overflow in ioctl processing</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-46294</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;dm: fix a buffer overflow in ioctl processing&lt;/p&gt;
&lt;p&gt;Tony Asleson (using Claude) found a buffer overflow in dm-ioctl in the
function retrieve_status:&lt;/p&gt;
&lt;p&gt;1. The code in retrieve_status checks that the output string fits into
   the output buffer and writes the output string there
2. Then, the code aligns the &amp;#34;outptr&amp;#34; variable to the next 8-byte
   boundary:
	outptr = align_ptr(outptr);
3. The alignment doesn&amp;#39;t check overflow, so outptr could point past the
   buffer end
4. The &amp;#34;for&amp;#34; loop is iterated again, it executes:
	remaining = len - (outptr - outbuf);
5. If &amp;#34;outptr&amp;#34; points past &amp;#34;outbuf + len&amp;#34;, the arithmetics wraps around
   and the variable &amp;#34;remaining&amp;#34; contains unusually high number
6. With &amp;#34;remaining&amp;#34; being high, the code writes more data past the end of
   the buffer&lt;/p&gt;
&lt;p&gt;Luckily, this bug has no security implications because:
1. Only root can issue device mapper ioctls
2. The commonly used libraries that communicate with device mapper
   (libdevmapper and devicemapper-rs) use buffer size that is aligned to
   8 bytes - thus, &amp;#34;outptr = align_ptr(outptr)&amp;#34; can&amp;#39;t overshoot the input
   buffer and the bug can&amp;#39;t happen accidentally&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;dm: fix a buffer overflow in ioctl processing&lt;/p&gt;
&lt;p&gt;Tony Asleson (using Claude) found a buffer overflow in dm-ioctl in the
function retrieve_status:&lt;/p&gt;
&lt;p&gt;1. The code in retrieve_status checks that the output string fits into
   the output buffer and writes the output string there
2. Then, the code aligns the &amp;#34;outptr&amp;#34; variable to the next 8-byte
   boundary:
	outptr = align_ptr(outptr);
3. The alignment doesn&amp;#39;t check overflow, so outptr could point past the
   buffer end
4. The &amp;#34;for&amp;#34; loop is iterated again, it executes:
	remaining = len - (outptr - outbuf);
5. If &amp;#34;outptr&amp;#34; points past &amp;#34;outbuf + len&amp;#34;, the arithmetics wraps around
   and the variable &amp;#34;remaining&amp;#34; contains unusually high number
6. With &amp;#34;remaining&amp;#34; being high, the code writes more data past the end of
   the buffer&lt;/p&gt;
&lt;p&gt;Luckily, this bug has no security implications because:
1. Only root can issue device mapper ioctls
2. The commonly used libraries that communicate with device mapper
   (libdevmapper and devicemapper-rs) use buffer size that is aligned to
   8 bytes - thus, &amp;#34;outptr = align_ptr(outptr)&amp;#34; can&amp;#39;t overshoot the input
   buffer and the bug can&amp;#39;t happen accidentally&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-46294</guid>
    </item>
  </channel>
</rss>
