<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-06T11:42:45.452361+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2026-64057</id>
    <title>CVE-2026-64057 — afs: Fix the locking used by afs_get_link()</title>
    <updated>2026-10-06T11:42:45.472757+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>afs: Fix the locking used by afs_get_link()</p>
<p>The afs filesystem in the kernel doesn't do locking correctly for symbolic
links.  There are a number of problems:</p>
<p>(1) It doesn't do any locking around afs_read_single() to prevent races
     between multiple -&gt;get_link() calls, thereby allowing the possibility
     of leaks.</p>
<p>(2) It doesn't use RCU barriering when accessing the buffer pointers
     during RCU pathwalk.</p>
<p>(3) It can race with another thread updating the contents of the symlink
     if a third party updated it on the server.</p>
<p>Fix this by the following means:</p>
<p>(0) Move symlink handling into its own file as this makes it more
     complicated.</p>
<p>(1) Take the validate_lock around afs_read_single() to prevent races
     between multiple -&gt;get_link() calls.</p>
<p>(2) Keep a separate copy of the symlink contents with an rcu_head.  This
     is always going to be a lot smaller than a page, so it can be
     kmalloc'd and save quite a bit of memory.  It also needs a refcount
     for non-RCU pathwalk.</p>
<p>(3) Split the symlink read and write-to-cache routines in afs from those
     for directories.</p>
<p>(4) Discard the I/O buffer as soon as the write-to-cache completes as this
     is a full page (plus a folio_queue).</p>
<p>(5) If there's no cache, discard the I/O buffer immediately after reading
     and copying if there is no cache.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-64057"/>
  </entry>
</feed>
