Answer in brief
CVE-2026-64371 records a Unknown severity vulnerability in proc: protect ptrace_may_access() with exec_update_lock (part 1). 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-64371 records a Unknown severity vulnerability in proc: protect ptrace_may_access() with exec_update_lock (part 1). 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 | >=f83ce3e6b02d5e48b3a43b001390e2b58820389d <ae1e630bcaac739f625822078edbaea98366930d || >=f83ce3e6b02d5e48b3a43b001390e2b58820389d <d54f14655fd7d7b293698a8b6918563c4c0465e7 || >=f83ce3e6b02d5e48b3a43b001390e2b58820389d <bb43679356f1f2a4c6b1c88aec4f021e5b5c74e9 || >=f83ce3e6b02d5e48b3a43b001390e2b58820389d <7456ae990a9738962b33146916fabca62ae3d4e0 || >=f83ce3e6b02d5e48b3a43b001390e2b58820389d <4bfe8c481846cee52473a2f7d7b30ee8e6749fc4 || >=f83ce3e6b02d5e48b3a43b001390e2b58820389d <f9b4b03ccc9c69bf7f7298d4559906ebea7143b3 || >=f83ce3e6b02d5e48b3a43b001390e2b58820389d <c1cfd63326f5d09999134e9052c353faf738286e || >=f83ce3e6b02d5e48b3a43b001390e2b58820389d <6650527444dadc63d84aa939d14ecba4fadb2f69 || 6b06d6282100dd5aacf7d45443d651a1995bd9c4 || 334ed22054b2ec8477e4409e214fc139cf937ef6 || >=2.6.27.23 <2.6.28 || >=2.6.29.3 <2.6.30 | ae1e630bcaac739f625822078edbaea98366930d, d54f14655fd7d7b293698a8b6918563c4c0465e7, bb43679356f1f2a4c6b1c88aec4f021e5b5c74e9, 7456ae990a9738962b33146916fabca62ae3d4e0, 4bfe8c481846cee52473a2f7d7b30ee8e6749fc4, f9b4b03ccc9c69bf7f7298d4559906ebea7143b3, c1cfd63326f5d09999134e9052c353faf738286e, 6650527444dadc63d84aa939d14ecba4fadb2f69, 2.6.28, 2.6.30 |
| Linux/Linuxgeneric | 2.6.30 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 11, 2026
In the Linux kernel, the following vulnerability has been resolved: proc: protect ptrace_may_access() with exec_update_lock (part 1) Fix the easy cases where procfs currently calls ptrace_may_access() without exec_update_lock protection, where the fix is to simply add the extra lock or use mm_access(): - do_task_stat(): grab exec_update_lock - proc_pid_wchan(): grab exec_update_lock - proc_map_files_lookup(): use mm_access() instead of get_task_mm() - proc_map_files_readdir(): use mm_access() instead of get_task_mm() - proc_ns_get_link(): grab exec_update_lock - proc_ns_readlink(): grab exec_update_lock
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 | >=f83ce3e6b02d5e48b3a43b001390e2b58820389d <ae1e630bcaac739f625822078edbaea98366930d || >=f83ce3e6b02d5e48b3a43b001390e2b58820389d <d54f14655fd7d7b293698a8b6918563c4c0465e7 || >=f83ce3e6b02d5e48b3a43b001390e2b58820389d <bb43679356f1f2a4c6b1c88aec4f021e5b5c74e9 || >=f83ce3e6b02d5e48b3a43b001390e2b58820389d <7456ae990a9738962b33146916fabca62ae3d4e0 || >=f83ce3e6b02d5e48b3a43b001390e2b58820389d <4bfe8c481846cee52473a2f7d7b30ee8e6749fc4 || >=f83ce3e6b02d5e48b3a43b001390e2b58820389d <f9b4b03ccc9c69bf7f7298d4559906ebea7143b3 || >=f83ce3e6b02d5e48b3a43b001390e2b58820389d <c1cfd63326f5d09999134e9052c353faf738286e || >=f83ce3e6b02d5e48b3a43b001390e2b58820389d <6650527444dadc63d84aa939d14ecba4fadb2f69 || 6b06d6282100dd5aacf7d45443d651a1995bd9c4 || 334ed22054b2ec8477e4409e214fc139cf937ef6 || >=2.6.27.23 <2.6.28 || >=2.6.29.3 <2.6.30 | ae1e630bcaac739f625822078edbaea98366930d, d54f14655fd7d7b293698a8b6918563c4c0465e7, bb43679356f1f2a4c6b1c88aec4f021e5b5c74e9, 7456ae990a9738962b33146916fabca62ae3d4e0, 4bfe8c481846cee52473a2f7d7b30ee8e6749fc4, f9b4b03ccc9c69bf7f7298d4559906ebea7143b3, c1cfd63326f5d09999134e9052c353faf738286e, 6650527444dadc63d84aa939d14ecba4fadb2f69, 2.6.28, 2.6.30 |
| Linux/Linuxgeneric | 2.6.30 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 11, 2026
In the Linux kernel, the following vulnerability has been resolved: proc: protect ptrace_may_access() with exec_update_lock (part 1) Fix the easy cases where procfs currently calls ptrace_may_access() without exec_update_lock protection, where the fix is to simply add the extra lock or use mm_access(): - do_task_stat(): grab exec_update_lock - proc_pid_wchan(): grab exec_update_lock - proc_map_files_lookup(): use mm_access() instead of get_task_mm() - proc_map_files_readdir(): use mm_access() instead of get_task_mm() - proc_ns_get_link(): grab exec_update_lock - proc_ns_readlink(): grab exec_update_lock
Quoted source text, attributed separately from HOL analysis.