<?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>Thu, 01 Oct 2026 20:31:01 +0000</lastBuildDate>
    <item>
      <title>UBUNTU-CVE-2021-47117</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2021-47117</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux and 108 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ext4: fix bug on in ext4_es_cache_extent as ext4_split_extent_at failed We got follow bug_on when run fsstress with injecting IO fault: [130747.323114] kernel BUG at fs/ext4/extents_status.c:762! [130747.323117] Internal error: Oops - BUG: 0 [#1] SMP ...... [130747.334329] Call trace: [130747.334553]  ext4_es_cache_extent+0x150/0x168 [ext4] [130747.334975]  ext4_cache_extents+0x64/0xe8 [ext4] [130747.335368]  ext4_find_extent+0x300/0x330 [ext4] [130747.335759]  ext4_ext_map_blocks+0x74/0x1178 [ext4] [130747.336179]  ext4_map_blocks+0x2f4/0x5f0 [ext4] [130747.336567]  ext4_mpage_readpages+0x4a8/0x7a8 [ext4] [130747.336995]  ext4_readpage+0x54/0x100 [ext4] [130747.337359]  generic_file_buffered_read+0x410/0xae8 [130747.337767]  generic_file_read_iter+0x114/0x190 [130747.338152]  ext4_file_read_iter+0x5c/0x140 [ext4] [130747.338556]  __vfs_read+0x11c/0x188 [130747.338851]  vfs_read+0x94/0x150 [130747.339110]  ksys_read+0x74/0xf0 This patch&amp;#39;s modification is according to Jan Kara&amp;#39;s suggestion in: https://patchwork.ozlabs.org/project/linux-ext4/patch/20210428085158.3728201-1-yebin10@huawei.com/ &amp;#34;I see. Now I understand your patch. Honestly, seeing how fragile is trying to fix extent tree after split has failed in the middle, I would probably go even further and make sure we fix the tree properly in case of ENOSPC and EDQUOT (those are easily user triggerable).  Anything else indicates a HW problem or fs corruptio…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux and 108 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ext4: fix bug on in ext4_es_cache_extent as ext4_split_extent_at failed We got follow bug_on when run fsstress with injecting IO fault: [130747.323114] kernel BUG at fs/ext4/extents_status.c:762! [130747.323117] Internal error: Oops - BUG: 0 [#1] SMP ...... [130747.334329] Call trace: [130747.334553]  ext4_es_cache_extent+0x150/0x168 [ext4] [130747.334975]  ext4_cache_extents+0x64/0xe8 [ext4] [130747.335368]  ext4_find_extent+0x300/0x330 [ext4] [130747.335759]  ext4_ext_map_blocks+0x74/0x1178 [ext4] [130747.336179]  ext4_map_blocks+0x2f4/0x5f0 [ext4] [130747.336567]  ext4_mpage_readpages+0x4a8/0x7a8 [ext4] [130747.336995]  ext4_readpage+0x54/0x100 [ext4] [130747.337359]  generic_file_buffered_read+0x410/0xae8 [130747.337767]  generic_file_read_iter+0x114/0x190 [130747.338152]  ext4_file_read_iter+0x5c/0x140 [ext4] [130747.338556]  __vfs_read+0x11c/0x188 [130747.338851]  vfs_read+0x94/0x150 [130747.339110]  ksys_read+0x74/0xf0 This patch&amp;#39;s modification is according to Jan Kara&amp;#39;s suggestion in: https://patchwork.ozlabs.org/project/linux-ext4/patch/20210428085158.3728201-1-yebin10@huawei.com/ &amp;#34;I see. Now I understand your patch. Honestly, seeing how fragile is trying to fix extent tree after split has failed in the middle, I would probably go even further and make sure we fix the tree properly in case of ENOSPC and EDQUOT (those are easily user triggerable).  Anything else indicates a HW problem or fs corruptio…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2021-47117</guid>
    </item>
  </channel>
</rss>
