<?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://cve.radiocsirt.org</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, 06 Oct 2026 06:44:54 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-46945 — ext4: always panic when errors=panic is specified</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2021-46945</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: always panic when errors=panic is specified&lt;/p&gt;
&lt;p&gt;Before commit 014c9caa29d3 (&amp;#34;ext4: make ext4_abort() use
__ext4_error()&amp;#34;), the following series of commands would trigger a
panic:&lt;/p&gt;
&lt;p&gt;1. mount /dev/sda -o ro,errors=panic test
2. mount /dev/sda -o remount,abort test&lt;/p&gt;
&lt;p&gt;After commit 014c9caa29d3, remounting a file system using the test
mount option &amp;#34;abort&amp;#34; will no longer trigger a panic.  This commit will
restore the behaviour immediately before commit 014c9caa29d3.
(However, note that the Linux kernel&amp;#39;s behavior has not been
consistent; some previous kernel versions, including 5.4 and 4.19
similarly did not panic after using the mount option &amp;#34;abort&amp;#34;.)&lt;/p&gt;
&lt;p&gt;This also makes a change to long-standing behaviour; namely, the
following series commands will now cause a panic, when previously it
did not:&lt;/p&gt;
&lt;p&gt;1. mount /dev/sda -o ro,errors=panic test
2. echo test &amp;gt; /sys/fs/ext4/sda/trigger_fs_error&lt;/p&gt;
&lt;p&gt;However, this makes ext4&amp;#39;s behaviour much more consistent, so this is
a good thing.&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: always panic when errors=panic is specified&lt;/p&gt;
&lt;p&gt;Before commit 014c9caa29d3 (&amp;#34;ext4: make ext4_abort() use
__ext4_error()&amp;#34;), the following series of commands would trigger a
panic:&lt;/p&gt;
&lt;p&gt;1. mount /dev/sda -o ro,errors=panic test
2. mount /dev/sda -o remount,abort test&lt;/p&gt;
&lt;p&gt;After commit 014c9caa29d3, remounting a file system using the test
mount option &amp;#34;abort&amp;#34; will no longer trigger a panic.  This commit will
restore the behaviour immediately before commit 014c9caa29d3.
(However, note that the Linux kernel&amp;#39;s behavior has not been
consistent; some previous kernel versions, including 5.4 and 4.19
similarly did not panic after using the mount option &amp;#34;abort&amp;#34;.)&lt;/p&gt;
&lt;p&gt;This also makes a change to long-standing behaviour; namely, the
following series commands will now cause a panic, when previously it
did not:&lt;/p&gt;
&lt;p&gt;1. mount /dev/sda -o ro,errors=panic test
2. echo test &amp;gt; /sys/fs/ext4/sda/trigger_fs_error&lt;/p&gt;
&lt;p&gt;However, this makes ext4&amp;#39;s behaviour much more consistent, so this is
a good thing.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2021-46945</guid>
    </item>
  </channel>
</rss>
