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.
Published: 2026-07-19
Score: 7.8 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The AFS filesystem in the Linux kernel does not protect symbolic link operations from concurrent access. afs_read_single() is invoked without proper locking and RCU barriers are missing, so multiple get_link calls can race and potentially expose internal buffer data. The flaw is a classic data‑race weakness (CWE‑367) that could allow an attacker to leak sensitive information or destabilise the filesystem when symbolic links are manipulated in parallel.

Affected Systems

All Linux kernel deployments that enable the AFS filesystem are affected. The advisory does not list specific kernel releases, so any build using the AFS module before the patch contains the flaw.

Risk and Exploitability

The CVSS score of 7.8 categorises the vulnerability as high severity, and the EPSS score of less than 1 % indicates a low but non‑zero likelihood of exploitation. The issue is not listed in the CISA KEV catalog, suggesting it has not yet been actively exploited. Because the flaw primarily accesses internal buffers without proper locking or RCU barriers, data leakage or instability can occur when symlinks are manipulated simultaneously by concurrent processes. Any user who performs symbolic link operations on an AFS mount can potentially trigger the vulnerability. Even though the exploitation probability is low, patching is advisable.

Generated by OpenCVE AI on July 30, 2026 at 20:49 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the kernel to a version that contains the CVE‑2026‑64057 fix, following the Linux kernel patch references or release notes.
  • If a kernel update cannot be performed immediately, unmount or otherwise disable AFS filesystems so that get_link operations cannot be performed until the patch is applied.
  • Reboot the system after updating the kernel to ensure all updated modules are loaded and the repair takes effect.

Generated by OpenCVE AI on July 30, 2026 at 20:49 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
History

Mon, 20 Jul 2026 14:45:00 +0000

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'}


Mon, 20 Jul 2026 12:15:00 +0000

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


Sun, 19 Jul 2026 16:15:00 +0000

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

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-05T12:38:46.858Z

Reserved: 2026-07-19T07:54:57.030Z

Link: CVE-2026-64057

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-07-19T00:00:00Z

Links: CVE-2026-64057 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-07-30T21:00:22Z

Weaknesses
  • CWE-367

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