<?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 02:16:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-54153 — ext4: turn quotas off if mount failed after enabling quotas</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-54153</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;ext4: turn quotas off if mount failed after enabling quotas&lt;/p&gt;
&lt;p&gt;Yi found during a review of the patch &amp;#34;ext4: don&amp;#39;t BUG on inconsistent
journal feature&amp;#34; that when ext4_mark_recovery_complete() returns an error
value, the error handling path does not turn off the enabled quotas,
which triggers the following kmemleak:&lt;/p&gt;
&lt;p&gt;================================================================
unreferenced object 0xffff8cf68678e7c0 (size 64):
comm &amp;#34;mount&amp;#34;, pid 746, jiffies 4294871231 (age 11.540s)
hex dump (first 32 bytes):
00 90 ef 82 f6 8c ff ff 00 00 00 00 41 01 00 00  ............A...
c7 00 00 00 bd 00 00 00 0a 00 00 00 48 00 00 00  ............H...
backtrace:
[&amp;lt;00000000c561ef24&amp;gt;] __kmem_cache_alloc_node+0x4d4/0x880
[&amp;lt;00000000d4e621d7&amp;gt;] kmalloc_trace+0x39/0x140
[&amp;lt;00000000837eee74&amp;gt;] v2_read_file_info+0x18a/0x3a0
[&amp;lt;0000000088f6c877&amp;gt;] dquot_load_quota_sb+0x2ed/0x770
[&amp;lt;00000000340a4782&amp;gt;] dquot_load_quota_inode+0xc6/0x1c0
[&amp;lt;0000000089a18bd5&amp;gt;] ext4_enable_quotas+0x17e/0x3a0 [ext4]
[&amp;lt;000000003a0268fa&amp;gt;] __ext4_fill_super+0x3448/0x3910 [ext4]
[&amp;lt;00000000b0f2a8a8&amp;gt;] ext4_fill_super+0x13d/0x340 [ext4]
[&amp;lt;000000004a9489c4&amp;gt;] get_tree_bdev+0x1dc/0x370
[&amp;lt;000000006e723bf1&amp;gt;] ext4_get_tree+0x1d/0x30 [ext4]
[&amp;lt;00000000c7cb663d&amp;gt;] vfs_get_tree+0x31/0x160
[&amp;lt;00000000320e1bed&amp;gt;] do_new_mount+0x1d5/0x480
[&amp;lt;00000000c074654c&amp;gt;] path_mount+0x22e/0xbe0
[&amp;lt;0000000003e97a8e&amp;gt;] do_mount+0x95/0xc0
[&amp;lt;000000002f3d3736&amp;gt;] __x64_sys_mount+0xc4/0x160
[&amp;lt;0000000027d21…&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;ext4: turn quotas off if mount failed after enabling quotas&lt;/p&gt;
&lt;p&gt;Yi found during a review of the patch &amp;#34;ext4: don&amp;#39;t BUG on inconsistent
journal feature&amp;#34; that when ext4_mark_recovery_complete() returns an error
value, the error handling path does not turn off the enabled quotas,
which triggers the following kmemleak:&lt;/p&gt;
&lt;p&gt;================================================================
unreferenced object 0xffff8cf68678e7c0 (size 64):
comm &amp;#34;mount&amp;#34;, pid 746, jiffies 4294871231 (age 11.540s)
hex dump (first 32 bytes):
00 90 ef 82 f6 8c ff ff 00 00 00 00 41 01 00 00  ............A...
c7 00 00 00 bd 00 00 00 0a 00 00 00 48 00 00 00  ............H...
backtrace:
[&amp;lt;00000000c561ef24&amp;gt;] __kmem_cache_alloc_node+0x4d4/0x880
[&amp;lt;00000000d4e621d7&amp;gt;] kmalloc_trace+0x39/0x140
[&amp;lt;00000000837eee74&amp;gt;] v2_read_file_info+0x18a/0x3a0
[&amp;lt;0000000088f6c877&amp;gt;] dquot_load_quota_sb+0x2ed/0x770
[&amp;lt;00000000340a4782&amp;gt;] dquot_load_quota_inode+0xc6/0x1c0
[&amp;lt;0000000089a18bd5&amp;gt;] ext4_enable_quotas+0x17e/0x3a0 [ext4]
[&amp;lt;000000003a0268fa&amp;gt;] __ext4_fill_super+0x3448/0x3910 [ext4]
[&amp;lt;00000000b0f2a8a8&amp;gt;] ext4_fill_super+0x13d/0x340 [ext4]
[&amp;lt;000000004a9489c4&amp;gt;] get_tree_bdev+0x1dc/0x370
[&amp;lt;000000006e723bf1&amp;gt;] ext4_get_tree+0x1d/0x30 [ext4]
[&amp;lt;00000000c7cb663d&amp;gt;] vfs_get_tree+0x31/0x160
[&amp;lt;00000000320e1bed&amp;gt;] do_new_mount+0x1d5/0x480
[&amp;lt;00000000c074654c&amp;gt;] path_mount+0x22e/0xbe0
[&amp;lt;0000000003e97a8e&amp;gt;] do_mount+0x95/0xc0
[&amp;lt;000000002f3d3736&amp;gt;] __x64_sys_mount+0xc4/0x160
[&amp;lt;0000000027d21…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-54153</guid>
    </item>
  </channel>
</rss>
