CVE Intelligence
Medium

CVE-2026-64371 — proc: protect ptrace_may_access() with exec_update_lock (part 1)

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

Published Jul 25, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: Linux

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.1% (30-day exploitation probability)+0
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.13%
ahead of 2% of scored CVEs · Oct 14, 2026
Affects
Linux
Linux and 1 more
CVSS base
5.5
Medium · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Linux Linux version 2.6.30≥ 2.6.29.3 and < 2.6.30≥ 2.6.27.23 and < 2.6.28version 334ed22054b2ec8477e4409e214fc139cf937ef6version 6b06d6282100dd5aacf7d45443d651a1995bd9c4≥ f83ce3e6b02d5e48b3a43b001390e2b58820389d and < 6650527444dadc63d84aa939d14ecba4fadb2f69≥ f83ce3e6b02d5e48b3a43b001390e2b58820389d and < c1cfd63326f5d09999134e9052c353faf738286e≥ f83ce3e6b02d5e48b3a43b001390e2b58820389d and < f9b4b03ccc9c69bf7f7298d4559906ebea7143b3
and 5 more ≥ f83ce3e6b02d5e48b3a43b001390e2b58820389d and < 4bfe8c481846cee52473a2f7d7b30ee8e6749fc4≥ f83ce3e6b02d5e48b3a43b001390e2b58820389d and < 7456ae990a9738962b33146916fabca62ae3d4e0≥ f83ce3e6b02d5e48b3a43b001390e2b58820389d and < bb43679356f1f2a4c6b1c88aec4f021e5b5c74e9≥ f83ce3e6b02d5e48b3a43b001390e2b58820389d and < d54f14655fd7d7b293698a8b6918563c4c0465e7≥ f83ce3e6b02d5e48b3a43b001390e2b58820389d and < ae1e630bcaac739f625822078edbaea98366930d
Vulnerable CVE Program (cve.org) e CISA ADP
Linux Linux Kernel version 2.6.30-rc8≥ 2.6.27.23 and < 2.6.28version 2.6.30-rc7version 2.6.30-rc6version 2.6.30-rc5version 2.6.30≥ 6.19 and < 7.1.4≥ 6.13 and < 6.18.40
and 6 more ≥ 6.7 and < 6.12.97≥ 6.2 and < 6.6.145≥ 5.16 and < 6.1.178≥ 5.11 and < 5.15.212≥ 2.6.30.1 and < 5.10.261≥ 2.6.29.3 and < 2.6.30
Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.5 CVSS 3.1 Medium 1.8 3.6 nvd@nist.gov via NIST National Vulnerability Database
5.5 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov)

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · linux/linux
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 15, 2026
  • Fix documented
    Oct 15, 2026 · NIST National Vulnerability Database
  • Affected products added · linux/linux kernel
    Oct 15, 2026 · NIST National Vulnerability Database
  • CVSS changed · 5.5
    Oct 15, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 15, 2026 · Alertas do Telegram
  • CVE published
    Jul 25, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 15, 2026 – Oct 15, 2026
  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

12 on the record

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

  • Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 8h
  • Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 8h
  • Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
  • Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
  • Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
  • Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CISA SSVC assessment.
  • No CWE classification.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-64371 is "proc: protect ptrace_may_access() with exec_update_lock (part 1)", rated Medium. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.13% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.