Answer in brief
CVE-2026-64057 records a High severity (CVSS 7.8) vulnerability in afs: Fix the locking used by afs_get_link(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=eae9e78951bb02a7b94a9adef6e981413d13c564 <77ea917cbed62882a33114b1e23ededb977e4287 || >=eae9e78951bb02a7b94a9adef6e981413d13c564 <c0410adf3da6db46f3513411fcf95e63c2f1d1ad | 77ea917cbed62882a33114b1e23ededb977e4287, c0410adf3da6db46f3513411fcf95e63c2f1d1ad |
| Linux/Linuxgeneric | 6.14 | Not reported |
| Linux/Linuxgeneric | >=eae9e78951bb02a7b94a9adef6e981413d13c564 <93531bca46707c6c28c4f4eb26c101fa36ccb8cb || >=eae9e78951bb02a7b94a9adef6e981413d13c564 <77ea917cbed62882a33114b1e23ededb977e4287 || >=eae9e78951bb02a7b94a9adef6e981413d13c564 <c0410adf3da6db46f3513411fcf95e63c2f1d1ad | 93531bca46707c6c28c4f4eb26c101fa36ccb8cb, 77ea917cbed62882a33114b1e23ededb977e4287, c0410adf3da6db46f3513411fcf95e63c2f1d1ad |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.