<?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>Wed, 07 Oct 2026 02:58:36 +0000</lastBuildDate>
    <item>
      <title>CVE-2020-16120 — Unprivileged overlay + shiftfs read access</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2020-16120</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux kernel&lt;/p&gt;
&lt;p&gt;Overlayfs did not properly perform permission checking when copying up files in an overlayfs and could be exploited from within a user namespace, if, for example, unprivileged user namespaces were allowed. It was possible to have a file not readable by an unprivileged user to be copied to a mountpoint controlled by the user, like a removable device. This was introduced in kernel version 4.19 by commit d1d04ef (&amp;#34;ovl: stack file ops&amp;#34;). This was fixed in kernel version 5.8 by commits 56230d9 (&amp;#34;ovl: verify permissions in ovl_path_open()&amp;#34;), 48bd024 (&amp;#34;ovl: switch to mounter creds in readdir&amp;#34;) and 05acefb (&amp;#34;ovl: check permission to open real file&amp;#34;). Additionally, commits 130fdbc (&amp;#34;ovl: pass correct flags for opening real directory&amp;#34;) and 292f902 (&amp;#34;ovl: call secutiry hook in ovl_real_ioctl()&amp;#34;) in kernel 5.8 might also be desired or necessary. These additional commits introduced a regression in overlay mounts within user namespaces which prevented access to files with ownership outside of the user namespace. This regression was mitigated by subsequent commit b6650da (&amp;#34;ovl: do not fail because of O_NOATIMEi&amp;#34;) in kernel 5.11.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux kernel&lt;/p&gt;
&lt;p&gt;Overlayfs did not properly perform permission checking when copying up files in an overlayfs and could be exploited from within a user namespace, if, for example, unprivileged user namespaces were allowed. It was possible to have a file not readable by an unprivileged user to be copied to a mountpoint controlled by the user, like a removable device. This was introduced in kernel version 4.19 by commit d1d04ef (&amp;#34;ovl: stack file ops&amp;#34;). This was fixed in kernel version 5.8 by commits 56230d9 (&amp;#34;ovl: verify permissions in ovl_path_open()&amp;#34;), 48bd024 (&amp;#34;ovl: switch to mounter creds in readdir&amp;#34;) and 05acefb (&amp;#34;ovl: check permission to open real file&amp;#34;). Additionally, commits 130fdbc (&amp;#34;ovl: pass correct flags for opening real directory&amp;#34;) and 292f902 (&amp;#34;ovl: call secutiry hook in ovl_real_ioctl()&amp;#34;) in kernel 5.8 might also be desired or necessary. These additional commits introduced a regression in overlay mounts within user namespaces which prevented access to files with ownership outside of the user namespace. This regression was mitigated by subsequent commit b6650da (&amp;#34;ovl: do not fail because of O_NOATIMEi&amp;#34;) in kernel 5.11.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2020-16120</guid>
    </item>
  </channel>
</rss>
