Answer in brief
CVE-2026-64375 records a Unknown severity vulnerability in proc: protect ptrace_may_access() with exec_update_lock (FD links). The current sources do not mark it as known exploited. The current feed maps 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.
Answer in brief
CVE-2026-64375 records a Unknown severity vulnerability in proc: protect ptrace_may_access() with exec_update_lock (FD links). The current sources do not mark it as known exploited. The current feed maps 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.
A CVSS score is not reported in the current record. 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=778c1144771f0064b6f51bee865cceb0d996f2f9 <6253dfee5afba536bb54fc6fe6c091c3758fafe1 || >=778c1144771f0064b6f51bee865cceb0d996f2f9 <65bf0d2b6e914f1448d6a2fde193dcf60936a651 || >=778c1144771f0064b6f51bee865cceb0d996f2f9 <de497d7aa2fae453a7e7c8f7d3e8682e565e3aaf || >=778c1144771f0064b6f51bee865cceb0d996f2f9 <138c692d2b2d63d26f2eb957d0e4fcc5d61f9ff2 || >=778c1144771f0064b6f51bee865cceb0d996f2f9 <83b17872e3166c295c599279fc9562ac3840c638 || >=778c1144771f0064b6f51bee865cceb0d996f2f9 <497c6bae5167428596575f20af6613ff5671f383 || >=778c1144771f0064b6f51bee865cceb0d996f2f9 <dfd1894cb64cbd8758b461ed713800fe73db4f82 || >=778c1144771f0064b6f51bee865cceb0d996f2f9 <6255da28d4bb5349fe18e84cb043ccd394eba75d | 6253dfee5afba536bb54fc6fe6c091c3758fafe1, 65bf0d2b6e914f1448d6a2fde193dcf60936a651, de497d7aa2fae453a7e7c8f7d3e8682e565e3aaf, 138c692d2b2d63d26f2eb957d0e4fcc5d61f9ff2, 83b17872e3166c295c599279fc9562ac3840c638, 497c6bae5167428596575f20af6613ff5671f383, dfd1894cb64cbd8758b461ed713800fe73db4f82, 6255da28d4bb5349fe18e84cb043ccd394eba75d |
| Linux/Linuxgeneric | 2.6.18 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 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: 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().
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=778c1144771f0064b6f51bee865cceb0d996f2f9 <6253dfee5afba536bb54fc6fe6c091c3758fafe1 || >=778c1144771f0064b6f51bee865cceb0d996f2f9 <65bf0d2b6e914f1448d6a2fde193dcf60936a651 || >=778c1144771f0064b6f51bee865cceb0d996f2f9 <de497d7aa2fae453a7e7c8f7d3e8682e565e3aaf || >=778c1144771f0064b6f51bee865cceb0d996f2f9 <138c692d2b2d63d26f2eb957d0e4fcc5d61f9ff2 || >=778c1144771f0064b6f51bee865cceb0d996f2f9 <83b17872e3166c295c599279fc9562ac3840c638 || >=778c1144771f0064b6f51bee865cceb0d996f2f9 <497c6bae5167428596575f20af6613ff5671f383 || >=778c1144771f0064b6f51bee865cceb0d996f2f9 <dfd1894cb64cbd8758b461ed713800fe73db4f82 || >=778c1144771f0064b6f51bee865cceb0d996f2f9 <6255da28d4bb5349fe18e84cb043ccd394eba75d | 6253dfee5afba536bb54fc6fe6c091c3758fafe1, 65bf0d2b6e914f1448d6a2fde193dcf60936a651, de497d7aa2fae453a7e7c8f7d3e8682e565e3aaf, 138c692d2b2d63d26f2eb957d0e4fcc5d61f9ff2, 83b17872e3166c295c599279fc9562ac3840c638, 497c6bae5167428596575f20af6613ff5671f383, dfd1894cb64cbd8758b461ed713800fe73db4f82, 6255da28d4bb5349fe18e84cb043ccd394eba75d |
| Linux/Linuxgeneric | 2.6.18 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 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: 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().
Quoted source text, attributed separately from HOL analysis.