CVE-2026-64371
Last modified
CVE-2026-64371 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.19% chance of exploitation in the next 30 days.
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
Metrics
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 2.6.27.23, < 2.6.28 |
| Linux | Linux Kernel | >= 2.6.29.3, < 2.6.30 |
| Linux | Linux Kernel | >= 2.6.30.1, < 5.10.261 |
| Linux | Linux Kernel | >= 5.11, < 5.15.212 |
| Linux | Linux Kernel | >= 5.16, < 6.1.178 |
| Linux | Linux Kernel | >= 6.2, < 6.6.145 |
| Linux | Linux Kernel | >= 6.7, < 6.12.97 |
| Linux | Linux Kernel | >= 6.13, < 6.18.40 |
| Linux | Linux Kernel | >= 6.19, < 7.1.4 |
| Linux | Linux Kernel | 2.6.30 |
References
- https://cert-portal.siemens.com/productcert/html/ssa-019113.htmlThird Party Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64371?
How severe is CVE-2026-64371?
How do I fix CVE-2026-64371?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64366In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64367In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64368In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2026-64369In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-6437Improper neutralization of argument delimiters in the volume…6.9
- CVE-2026-64370In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64372In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64373In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2026-64374In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-64375In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64376In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64377In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-64371?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
