0.0
NA
CVE-2026-64216
netfs: Fix potential UAF in netfs_unlock_abandoned_read_pages()
Description

In the Linux kernel, the following vulnerability has been resolved: netfs: Fix potential UAF in netfs_unlock_abandoned_read_pages() netfs_unlock_abandoned_read_pages(rreq) accesses the index of the folios it is wanting to unlock and compares that to rreq->no_unlock_folio so that it doesn't unlock a folio being read for netfs_perform_write() or netfs_write_begin(). However, given that netfs_unlock_abandoned_read_pages() is called _after_ NETFS_RREQ_IN_PROGRESS is cleared, the one folio that it's not allowed to dereference is the one specified by ->no_unlock_folio as ownership immediately reverts to the caller. Fix this by storing the folio pointer instead and using that rather than the index. Also fix netfs_unlock_read_folio() where the same applies.

INFO

Published Date :

July 24, 2026, 4:16 p.m.

Last Modified :

July 24, 2026, 4:16 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2026-64216 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

Solution
Apply Linux kernel patches to fix a use-after-free vulnerability in netfs.
  • Update the Linux kernel to the latest version.
  • Apply the specific netfs patch for the vulnerability.
  • Reboot the system after applying the update.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-64216.

URL Resource
https://git.kernel.org/stable/c/3866d015f33aeedf81338dd99154703bef33faef
https://git.kernel.org/stable/c/6080fa3ecfbb4448a3b47368629534c09b6ec750
https://git.kernel.org/stable/c/dbe556972100fabb8e5a1b3d2163831ff07b1e8e
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-64216 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-64216 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-64216 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-64216 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Jul. 24, 2026

    Action Type Old Value New Value
    Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': 'ee4cdf7ba857a894ad1650d6ab77669cbbfa329e', 'lessThan': '6080fa3ecfbb4448a3b47368629534c09b6ec750', 'versionType': 'git'}, {'status': 'affected', 'version': 'ee4cdf7ba857a894ad1650d6ab77669cbbfa329e', 'lessThan': '3866d015f33aeedf81338dd99154703bef33faef', 'versionType': 'git'}, {'status': 'affected', 'version': 'ee4cdf7ba857a894ad1650d6ab77669cbbfa329e', 'lessThan': 'dbe556972100fabb8e5a1b3d2163831ff07b1e8e', 'versionType': 'git'}], 'programFiles': ['fs/netfs/buffered_read.c', 'fs/netfs/read_collect.c', 'fs/netfs/read_retry.c', 'include/linux/netfs.h'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '6.12'}, {'status': 'unaffected', 'version': '0', 'lessThan': '6.12', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.18.34', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.11', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['fs/netfs/buffered_read.c', 'fs/netfs/read_collect.c', 'fs/netfs/read_retry.c', 'include/linux/netfs.h'], 'defaultStatus': 'affected'}]
    Added Description In the Linux kernel, the following vulnerability has been resolved: netfs: Fix potential UAF in netfs_unlock_abandoned_read_pages() netfs_unlock_abandoned_read_pages(rreq) accesses the index of the folios it is wanting to unlock and compares that to rreq->no_unlock_folio so that it doesn't unlock a folio being read for netfs_perform_write() or netfs_write_begin(). However, given that netfs_unlock_abandoned_read_pages() is called _after_ NETFS_RREQ_IN_PROGRESS is cleared, the one folio that it's not allowed to dereference is the one specified by ->no_unlock_folio as ownership immediately reverts to the caller. Fix this by storing the folio pointer instead and using that rather than the index. Also fix netfs_unlock_read_folio() where the same applies.
    Added Reference https://git.kernel.org/stable/c/3866d015f33aeedf81338dd99154703bef33faef
    Added Reference https://git.kernel.org/stable/c/6080fa3ecfbb4448a3b47368629534c09b6ec750
    Added Reference https://git.kernel.org/stable/c/dbe556972100fabb8e5a1b3d2163831ff07b1e8e
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.