0.0
NA
CVE-2026-64375
proc: protect ptrace_may_access() with exec_update_lock (FD links)
Description

In the Linux kernel, the following vulnerability has been resolved: proc: protect ptrace_may_access() with exec_update_lock (FD links) proc_pid_get_link() and proc_pid_readlink() currently look up the task from the pid once, then do the ptrace access check on that task, then look up the task from the pid a second time to do the actual access. That's racy in several ways. To fix it, pass the task to the ->proc_get_link() handler, and instead of proc_fd_access_allowed(), introduce a new helper call_proc_get_link() that looks up and locks the task, does the access check, and calls ->proc_get_link().

INFO

Published Date :

July 25, 2026, 10:17 a.m.

Last Modified :

July 25, 2026, 10:17 a.m.

Remotely Exploit :

No

Source :

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

The following products are affected by CVE-2026-64375 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
Address race conditions in procfs by locking and validating task access before operations.
  • Apply kernel patches to protect ptrace_may_access.
  • Update the kernel to include exec_update_lock protection.
  • Ensure task lookups are locked during access checks.
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-64375 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-64375 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-64375 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-64375 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. 25, 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': '778c1144771f0064b6f51bee865cceb0d996f2f9', 'lessThan': '6253dfee5afba536bb54fc6fe6c091c3758fafe1', 'versionType': 'git'}, {'status': 'affected', 'version': '778c1144771f0064b6f51bee865cceb0d996f2f9', 'lessThan': '65bf0d2b6e914f1448d6a2fde193dcf60936a651', 'versionType': 'git'}, {'status': 'affected', 'version': '778c1144771f0064b6f51bee865cceb0d996f2f9', 'lessThan': 'de497d7aa2fae453a7e7c8f7d3e8682e565e3aaf', 'versionType': 'git'}, {'status': 'affected', 'version': '778c1144771f0064b6f51bee865cceb0d996f2f9', 'lessThan': '138c692d2b2d63d26f2eb957d0e4fcc5d61f9ff2', 'versionType': 'git'}, {'status': 'affected', 'version': '778c1144771f0064b6f51bee865cceb0d996f2f9', 'lessThan': '83b17872e3166c295c599279fc9562ac3840c638', 'versionType': 'git'}, {'status': 'affected', 'version': '778c1144771f0064b6f51bee865cceb0d996f2f9', 'lessThan': '497c6bae5167428596575f20af6613ff5671f383', 'versionType': 'git'}, {'status': 'affected', 'version': '778c1144771f0064b6f51bee865cceb0d996f2f9', 'lessThan': 'dfd1894cb64cbd8758b461ed713800fe73db4f82', 'versionType': 'git'}, {'status': 'affected', 'version': '778c1144771f0064b6f51bee865cceb0d996f2f9', 'lessThan': '6255da28d4bb5349fe18e84cb043ccd394eba75d', 'versionType': 'git'}], 'programFiles': ['fs/proc/base.c', 'fs/proc/fd.c', 'fs/proc/internal.h'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '2.6.18'}, {'status': 'unaffected', 'version': '0', 'lessThan': '2.6.18', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.10.261', 'versionType': 'semver', 'lessThanOrEqual': '5.10.*'}, {'status': 'unaffected', 'version': '5.15.212', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.178', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.145', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.97', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.40', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.4', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['fs/proc/base.c', 'fs/proc/fd.c', 'fs/proc/internal.h'], 'defaultStatus': 'affected'}]
    Added Description In the Linux kernel, the following vulnerability has been resolved: proc: protect ptrace_may_access() with exec_update_lock (FD links) proc_pid_get_link() and proc_pid_readlink() currently look up the task from the pid once, then do the ptrace access check on that task, then look up the task from the pid a second time to do the actual access. That's racy in several ways. To fix it, pass the task to the ->proc_get_link() handler, and instead of proc_fd_access_allowed(), introduce a new helper call_proc_get_link() that looks up and locks the task, does the access check, and calls ->proc_get_link().
    Added Reference https://git.kernel.org/stable/c/138c692d2b2d63d26f2eb957d0e4fcc5d61f9ff2
    Added Reference https://git.kernel.org/stable/c/497c6bae5167428596575f20af6613ff5671f383
    Added Reference https://git.kernel.org/stable/c/6253dfee5afba536bb54fc6fe6c091c3758fafe1
    Added Reference https://git.kernel.org/stable/c/6255da28d4bb5349fe18e84cb043ccd394eba75d
    Added Reference https://git.kernel.org/stable/c/65bf0d2b6e914f1448d6a2fde193dcf60936a651
    Added Reference https://git.kernel.org/stable/c/83b17872e3166c295c599279fc9562ac3840c638
    Added Reference https://git.kernel.org/stable/c/de497d7aa2fae453a7e7c8f7d3e8682e565e3aaf
    Added Reference https://git.kernel.org/stable/c/dfd1894cb64cbd8758b461ed713800fe73db4f82
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.