CVE-2026-64057

afs: Fix the locking used by afs_get_link()

Published Jul 19, 2026 CVSS 3.1 · 7.8 High EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

afs: Fix the locking used by afs_get_link()

The afs filesystem in the kernel doesn't do locking correctly for symbolic
links. There are a number of problems:

(1) It doesn't do any locking around afs_read_single() to prevent races
between multiple ->get_link() calls, thereby allowing the possibility
of leaks.

(2) It doesn't use RCU barriering when accessing the buffer pointers
during RCU pathwalk.

(3) It can race with another thread updating the contents of the symlink
if a third party updated it on the server.

Fix this by the following means:

(0) Move symlink handling into its own file as this makes it more
complicated.

(1) Take the validate_lock around afs_read_single() to prevent races
between multiple ->get_link() calls.

(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.

(3) Split the symlink read and write-to-cache routines in afs from those
for directories.

(4) Discard the I/O buffer as soon as the write-to-cache completes as this
is a full page (plus a folio_queue).

(5) If there's no cache, discard the I/O buffer immediately after reading
and copying if there is no cache.

Analysis

AI-generated

Technical impact

The AFS filesystem in the Linux kernel has a flaw in how it handles symbolic links. The kernel does not acquire the validate_lock when performing afs_read_single() and it omits RCU barriers during RCU pathwalk. These omissions allow concurrent get_link() calls to race, potentially exposing internal buffer contents or corrupting the symlink data. The weakness exhibits classic data‑race behaviour (CWE‑367) and can also lead to improper synchronization problems (CWE‑667). An attacker who can trigger symbolic‑link reads in parallel may cause the kernel to leak sensitive data or destabilise the filesystem.

Affected Systems

Any Linux kernel that includes the AFS module is affected. The advisory references kernel releases 7.1 rc1 through rc4 in the CPE list, implying those versions run the vulnerable code. Because AFS is a loadable module, any kernel that has the module built or loaded prior to the patch also contains the flaw.

Risk and Exploitability

The CVSS score of 7.8 classifies this vulnerability as high severity. The EPSS score of less than 1 % indicates a low but non‑zero chance of exploitation, and it is not listed in the CISA KEV catalog. Based on the description, the flaw can be exploited by an attacker who has local access to an AFS mount or who can manipulate symbolic links through an AFS process. The likely attack vector is inferred to be local or privileged, rather than remote, with the goal of reading memory or destabilising the filesystem. Although exploitation is unlikely, the impact of a data leak or filesystem instability justifies immediate patching.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the kernel to a release that includes the CVE‑2026‑64057 fix, using the patch references or release notes from the Linux kernel development community.
  • If a kernel upgrade cannot be performed right away, unmount or disable all AFS filesystems so that get_link operations cannot be performed until the patch is applied.
  • Reboot the system after updating the kernel to ensure the updated module is loaded and the repair takes effect.

Generated by OpenCVE AI on September 3, 2026 at 14:43 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8593-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8603-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8618-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8663-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8664-1 Linux kernel (NVIDIA BaseOS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-1 Linux kernel (GCP) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-2 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-3 Linux kernel (Oracle) vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-667
CPEs cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:*
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
Weaknesses CWE-367
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: afs: Fix the locking used by afs_get_link() The afs filesystem in the kernel doesn't do locking correctly for symbolic links. There are a number of problems: (1) It doesn't do any locking around afs_read_single() to prevent races between multiple ->get_link() calls, thereby allowing the possibility of leaks. (2) It doesn't use RCU barriering when accessing the buffer pointers during RCU pathwalk. (3) It can race with another thread updating the contents of the symlink if a third party updated it on the server. Fix this by the following means: (0) Move symlink handling into its own file as this makes it more complicated. (1) Take the validate_lock around afs_read_single() to prevent races between multiple ->get_link() calls. (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. (3) Split the symlink read and write-to-cache routines in afs from those for directories. (4) Discard the I/O buffer as soon as the write-to-cache completes as this is a full page (plus a folio_queue). (5) If there's no cache, discard the I/O buffer immediately after reading and copying if there is no cache.
Title afs: Fix the locking used by afs_get_link()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-367

    Time-of-check Time-of-use (TOCTOU) Race Condition

  • CWE-667

    Improper Locking

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 15, 2026, 10:07 AM
Reserved
Jul 19, 2026, 7:54 AM
Status
Modified
Published
Jul 19, 2026, 4:17 PM
Modified
Oct 15, 2026, 11:17 AM
Severity
Moderate
Public date
Jul 19, 2026, 12:00 AM