CVE-2026-64371

Awaiting Analysis Awaiting Analysis - Queue

Race Condition in Linux Kernel procfs

Publication date: 2026-07-25

Last updated on: 2026-08-11

Assigner: kernel.org

Description

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

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-25

Last Modified

2026-08-11

Generated

2026-08-14

AI Q&A

2026-07-25

EPSS Evaluated

2026-08-13

NVD

CVE-2026-64371

EUVD

EUVD-2026-48915

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability in the Linux kernel involves improper protection of the ptrace_may_access() function in procfs. The issue occurs when procfs calls ptrace_may_access() without proper locking, potentially allowing unauthorized access to process memory or sensitive information. The fix involves adding exec_update_lock protection or using mm_access() in specific procfs functions.

Detection Guidance

This vulnerability is specific to the Linux kernel's proc filesystem and does not have a direct network detection method. To check if your system is vulnerable, verify the kernel version and confirm whether the described functions (do_task_stat, proc_pid_wchan, etc.) are using exec_update_lock or mm_access() as required. Use commands like uname -a to check the kernel version and inspect the kernel source code for the proc filesystem implementation.

Impact Analysis

This vulnerability could allow an attacker with local access to exploit race conditions in procfs to gain unauthorized access to process memory or sensitive data. This might lead to information disclosure, privilege escalation, or other malicious activities depending on the system configuration.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR, HIPAA, or similar standards as it pertains to a Linux kernel memory access control issue rather than data protection or privacy requirements.

Mitigation Strategies

Apply the latest kernel security updates provided by your Linux distribution to ensure the vulnerable functions are patched. If you are running a custom kernel, manually apply the described fixes by adding exec_update_lock protection or using mm_access() in the specified functions. Reboot the system after applying updates to activate the changes.

Hi! I’m here to help you understand CVE-2026-64371. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70