<?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>Wed, 30 Sep 2026 23:33:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49276 — jffs2: fix memory leak in jffs2_scan_medium</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-49276</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;jffs2: fix memory leak in jffs2_scan_medium&lt;/p&gt;
&lt;p&gt;If an error is returned in jffs2_scan_eraseblock() and some memory
has been added to the jffs2_summary *s, we can observe the following
kmemleak report:&lt;/p&gt;
&lt;p&gt;--------------------------------------------
unreferenced object 0xffff88812b889c40 (size 64):
  comm &amp;#34;mount&amp;#34;, pid 692, jiffies 4294838325 (age 34.288s)
  hex dump (first 32 bytes):
    40 48 b5 14 81 88 ff ff 01 e0 31 00 00 00 50 00  @H........1...P.
    00 00 01 00 00 00 01 00 00 00 02 00 00 00 09 08  ................
  backtrace:
    [&amp;lt;ffffffffae93a3a3&amp;gt;] __kmalloc+0x613/0x910
    [&amp;lt;ffffffffaf423b9c&amp;gt;] jffs2_sum_add_dirent_mem+0x5c/0xa0
    [&amp;lt;ffffffffb0f3afa8&amp;gt;] jffs2_scan_medium.cold+0x36e5/0x4794
    [&amp;lt;ffffffffb0f3dbe1&amp;gt;] jffs2_do_mount_fs.cold+0xa7/0x2267
    [&amp;lt;ffffffffaf40acf3&amp;gt;] jffs2_do_fill_super+0x383/0xc30
    [&amp;lt;ffffffffaf40c00a&amp;gt;] jffs2_fill_super+0x2ea/0x4c0
    [&amp;lt;ffffffffb0315d64&amp;gt;] mtd_get_sb+0x254/0x400
    [&amp;lt;ffffffffb0315f5f&amp;gt;] mtd_get_sb_by_nr+0x4f/0xd0
    [&amp;lt;ffffffffb0316478&amp;gt;] get_tree_mtd+0x498/0x840
    [&amp;lt;ffffffffaf40bd15&amp;gt;] jffs2_get_tree+0x25/0x30
    [&amp;lt;ffffffffae9f358d&amp;gt;] vfs_get_tree+0x8d/0x2e0
    [&amp;lt;ffffffffaea7a98f&amp;gt;] path_mount+0x50f/0x1e50
    [&amp;lt;ffffffffaea7c3d7&amp;gt;] do_mount+0x107/0x130
    [&amp;lt;ffffffffaea7c5c5&amp;gt;] __se_sys_mount+0x1c5/0x2f0
    [&amp;lt;ffffffffaea7c917&amp;gt;] __x64_sys_mount+0xc7/0x160
    [&amp;lt;ffffffffb10142f5&amp;gt;] do_syscall_64+0x45/0x70
unreferenced object 0xffff888114b54840 (size 32):
  comm &amp;#34;m…&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;jffs2: fix memory leak in jffs2_scan_medium&lt;/p&gt;
&lt;p&gt;If an error is returned in jffs2_scan_eraseblock() and some memory
has been added to the jffs2_summary *s, we can observe the following
kmemleak report:&lt;/p&gt;
&lt;p&gt;--------------------------------------------
unreferenced object 0xffff88812b889c40 (size 64):
  comm &amp;#34;mount&amp;#34;, pid 692, jiffies 4294838325 (age 34.288s)
  hex dump (first 32 bytes):
    40 48 b5 14 81 88 ff ff 01 e0 31 00 00 00 50 00  @H........1...P.
    00 00 01 00 00 00 01 00 00 00 02 00 00 00 09 08  ................
  backtrace:
    [&amp;lt;ffffffffae93a3a3&amp;gt;] __kmalloc+0x613/0x910
    [&amp;lt;ffffffffaf423b9c&amp;gt;] jffs2_sum_add_dirent_mem+0x5c/0xa0
    [&amp;lt;ffffffffb0f3afa8&amp;gt;] jffs2_scan_medium.cold+0x36e5/0x4794
    [&amp;lt;ffffffffb0f3dbe1&amp;gt;] jffs2_do_mount_fs.cold+0xa7/0x2267
    [&amp;lt;ffffffffaf40acf3&amp;gt;] jffs2_do_fill_super+0x383/0xc30
    [&amp;lt;ffffffffaf40c00a&amp;gt;] jffs2_fill_super+0x2ea/0x4c0
    [&amp;lt;ffffffffb0315d64&amp;gt;] mtd_get_sb+0x254/0x400
    [&amp;lt;ffffffffb0315f5f&amp;gt;] mtd_get_sb_by_nr+0x4f/0xd0
    [&amp;lt;ffffffffb0316478&amp;gt;] get_tree_mtd+0x498/0x840
    [&amp;lt;ffffffffaf40bd15&amp;gt;] jffs2_get_tree+0x25/0x30
    [&amp;lt;ffffffffae9f358d&amp;gt;] vfs_get_tree+0x8d/0x2e0
    [&amp;lt;ffffffffaea7a98f&amp;gt;] path_mount+0x50f/0x1e50
    [&amp;lt;ffffffffaea7c3d7&amp;gt;] do_mount+0x107/0x130
    [&amp;lt;ffffffffaea7c5c5&amp;gt;] __se_sys_mount+0x1c5/0x2f0
    [&amp;lt;ffffffffaea7c917&amp;gt;] __x64_sys_mount+0xc7/0x160
    [&amp;lt;ffffffffb10142f5&amp;gt;] do_syscall_64+0x45/0x70
unreferenced object 0xffff888114b54840 (size 32):
  comm &amp;#34;m…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-49276</guid>
    </item>
  </channel>
</rss>
