<?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://db.gcve.eu</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>Wed, 30 Sep 2026 19:00:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-93048 — mtd: part: reject MTDPART_OFS_RETAIN in mtd_add_partition()</title>
      <link>https://db.gcve.eu/vuln/cve-2026-93048</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;mtd: part: reject MTDPART_OFS_RETAIN in mtd_add_partition()&lt;/p&gt;
&lt;p&gt;mtd_add_partition() does not reject the special offset value
MTDPART_OFS_RETAIN (-3), which leads to a WARN_ON in
add_mtd_device() when called through the BLKPG ioctl on NAND
devices. The RETAIN value depends on cur_offset being the end of
the previous partition, but in the dynamic partition path
cur_offset equals the offset argument itself, causing undefined
behavior.&lt;/p&gt;
&lt;p&gt;Commit 5daa7b21496a (&amp;#34;mtd: prepare partition add and del functions
for ioctl requests&amp;#34;) introduced mtd_add_partition() and correctly
rejected MTDPART_OFS_APPEND (-1) and MTDPART_OFS_NXTBLK (-2),
since those special offsets rely on cur_offset tracking the
previous partition&amp;#39;s end. However, commit 1a31368bf92e (&amp;#34;mtd: add a flags
for partitions which should just leave smth. after them&amp;#34;)
later added MTDPART_OFS_RETAIN (-3) for the static
partition table path without updating mtd_add_partition() to
also reject this value.&lt;/p&gt;
&lt;p&gt;With offset=-3 passed via BLKPG, the RETAIN size calculation in
allocate_partition() underflows (parent_size - 0xFFFFFFFFFFFFFFFD
= parent_size + 3). If the underflow result does not appear to
leave enough space, allocate_partition() jumps to out_register via
goto, skipping erasesize initialization. This results in
erasesize=0, which triggers:&lt;/p&gt;
&lt;p&gt;WARN_ON((!mtd-&amp;gt;erasesize || !master-&amp;gt;_erase) &amp;amp;&amp;amp;
		!(mtd-&amp;gt;flags &amp;amp; MTD_NO_ERASE))&lt;/p&gt;
&lt;p&gt;in add_mtd_device(). If the underflow result…&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;mtd: part: reject MTDPART_OFS_RETAIN in mtd_add_partition()&lt;/p&gt;
&lt;p&gt;mtd_add_partition() does not reject the special offset value
MTDPART_OFS_RETAIN (-3), which leads to a WARN_ON in
add_mtd_device() when called through the BLKPG ioctl on NAND
devices. The RETAIN value depends on cur_offset being the end of
the previous partition, but in the dynamic partition path
cur_offset equals the offset argument itself, causing undefined
behavior.&lt;/p&gt;
&lt;p&gt;Commit 5daa7b21496a (&amp;#34;mtd: prepare partition add and del functions
for ioctl requests&amp;#34;) introduced mtd_add_partition() and correctly
rejected MTDPART_OFS_APPEND (-1) and MTDPART_OFS_NXTBLK (-2),
since those special offsets rely on cur_offset tracking the
previous partition&amp;#39;s end. However, commit 1a31368bf92e (&amp;#34;mtd: add a flags
for partitions which should just leave smth. after them&amp;#34;)
later added MTDPART_OFS_RETAIN (-3) for the static
partition table path without updating mtd_add_partition() to
also reject this value.&lt;/p&gt;
&lt;p&gt;With offset=-3 passed via BLKPG, the RETAIN size calculation in
allocate_partition() underflows (parent_size - 0xFFFFFFFFFFFFFFFD
= parent_size + 3). If the underflow result does not appear to
leave enough space, allocate_partition() jumps to out_register via
goto, skipping erasesize initialization. This results in
erasesize=0, which triggers:&lt;/p&gt;
&lt;p&gt;WARN_ON((!mtd-&amp;gt;erasesize || !master-&amp;gt;_erase) &amp;amp;&amp;amp;
		!(mtd-&amp;gt;flags &amp;amp; MTD_NO_ERASE))&lt;/p&gt;
&lt;p&gt;in add_mtd_device(). If the underflow result…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-93048</guid>
    </item>
  </channel>
</rss>
