<?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>Mon, 05 Oct 2026 21:44:32 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49688 — afs: Fix dynamic root getattr</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-49688</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;afs: Fix dynamic root getattr&lt;/p&gt;
&lt;p&gt;The recent patch to make afs_getattr consult the server didn&amp;#39;t account
for the pseudo-inodes employed by the dynamic root-type afs superblock
not having a volume or a server to access, and thus an oops occurs if
such a directory is stat&amp;#39;d.&lt;/p&gt;
&lt;p&gt;Fix this by checking to see if the vnode-&amp;gt;volume pointer actually points
anywhere before following it in afs_getattr().&lt;/p&gt;
&lt;p&gt;This can be tested by stat&amp;#39;ing a directory in /afs.  It may be
sufficient just to do &amp;#34;ls /afs&amp;#34; and the oops looks something like:&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000020
        ...
        RIP: 0010:afs_getattr+0x8b/0x14b
        ...
        Call Trace:
         &amp;lt;TASK&amp;gt;
         vfs_statx+0x79/0xf5
         vfs_fstatat+0x49/0x62&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;afs: Fix dynamic root getattr&lt;/p&gt;
&lt;p&gt;The recent patch to make afs_getattr consult the server didn&amp;#39;t account
for the pseudo-inodes employed by the dynamic root-type afs superblock
not having a volume or a server to access, and thus an oops occurs if
such a directory is stat&amp;#39;d.&lt;/p&gt;
&lt;p&gt;Fix this by checking to see if the vnode-&amp;gt;volume pointer actually points
anywhere before following it in afs_getattr().&lt;/p&gt;
&lt;p&gt;This can be tested by stat&amp;#39;ing a directory in /afs.  It may be
sufficient just to do &amp;#34;ls /afs&amp;#34; and the oops looks something like:&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000020
        ...
        RIP: 0010:afs_getattr+0x8b/0x14b
        ...
        Call Trace:
         &amp;lt;TASK&amp;gt;
         vfs_statx+0x79/0xf5
         vfs_fstatat+0x49/0x62&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-49688</guid>
    </item>
  </channel>
</rss>
