Skip to main content

Linux Kernel CVE-2026-64057

| EUVDEUVD-2026-45630 HIGH
Improper Locking (CWE-667)
2026-07-19 Linux GHSA-8264-g9fh-vx2h
7.8
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
5.8 MEDIUM

Local unprivileged access (AV:L/PR:L) and a timing-dependent symlink RCU/locking race (AC:H); impact is chiefly kernel memory disclosure (C:H) with limited integrity/availability effects.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:L
4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N
SUSE
HIGH
qualitative
Red Hat
5.5 MEDIUM
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jul 20, 2026 - 17:10 vuln.today
CVSS changed
Jul 20, 2026 - 15:22 NVD
7.8 (HIGH)
Patch available
Jul 19, 2026 - 17:03 EUVD
CVE Published
Jul 19, 2026 - 15:39 cve.org
UNKNOWN (no severity yet)
CVE Published
Jul 19, 2026 - 15:39 cve.org
HIGH 7.8

DescriptionCVE.org

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.

AnalysisAI

Improper locking in the Linux kernel AFS (Andrew File System) client's symbolic link handling (afs_get_link()) allows a local attacker on a host mounting an AFS volume to trigger race conditions that leak kernel memory and can expose stale or freed symlink buffers. The flaw affects kernels from roughly 6.14 up to the fixed 7.0.11/7.1 stable series and stems from a missing validate_lock, absent RCU barriering during lockless pathwalk, and unsynchronized access when a symlink is concurrently updated on the server. No public exploit identified at time of analysis; EPSS is low (0.15%, 5th percentile) and it is not on CISA KEV.

Technical ContextAI

The vulnerability lives in the kernel AFS filesystem client (fs/afs), a network filesystem used to reach OpenAFS/AuriStorFS servers. The ->get_link() inode operation resolves symbolic-link targets; the buggy code invoked afs_read_single() without holding validate_lock, failed to use RCU barriers when dereferencing buffer pointers during RCU pathwalk, and shared its read/write-to-cache routines with directory handling. The root-cause class is a concurrency/race defect (CWE reported as N/A, but consistent with CWE-362): multiple concurrent ->get_link() callers, RCU readers, and server-side symlink updates can interleave over the same I/O buffer, risking leaks and use of stale/freed data. The fix isolates symlink handling in its own file, takes validate_lock around the read, keeps a separately kmalloc'd refcounted copy of the symlink contents with an rcu_head, and discards I/O buffers promptly after caching or reading.

RemediationAI

Vendor-released patch: upgrade to a Linux stable kernel containing the fix - the 7.0.11 or 7.1 series (upstream commits at https://git.kernel.org/stable/c/77ea917cbed62882a33114b1e23ededb977e4287 and https://git.kernel.org/stable/c/c0410adf3da6db46f3513411fcf95e63c2f1d1ad) - by applying your distribution's corresponding kernel update and rebooting. If immediate patching is not possible and AFS is not needed, the most effective compensating control is to not load the AFS client: unmount any AFS volumes and blacklist the module (e.g. 'blacklist kafs' plus 'install kafs /bin/true' in modprobe config), with the trade-off that the host loses all AFS access - acceptable where AFS is unused. Where AFS is required, restrict local access to trusted users since exploitation needs a local account, and prioritize the kernel upgrade.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

CVE-2026-64057 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy