VulnerabilityPublished 25 Jul 2026Updated 6 Nov 2026

CVE-2026-64371: Linux kernel · part 1

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in f9b4b03ccc9c69bf7f7298d4559906ebea7143b3 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:04 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch

Available – fixed in f9b4b03ccc9c69bf7f7298d4559906ebea7143b3, d54f14655fd7d7b293698a8b6918563c4c0465e7, c1cfd63326f5d09999134e9052c353faf738286e +7

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected >=2.6.27.23 <2.6.28 >=2.6.29.3 <2.6.30	Fixed in f9b4b03ccc9c69bf7f7298d4559906ebea7143b3 d54f14655fd7d7b293698a8b6918563c4c0465e7 c1cfd63326f5d09999134e9052c353faf738286e bb43679356f1f2a4c6b1c88aec4f021e5b5c74e9 ae1e630bcaac739f625822078edbaea98366930d 6650527444dadc63d84aa939d14ecba4fadb2f69 7456ae990a9738962b33146916fabca62ae3d4e0 4bfe8c481846cee52473a2f7d7b30ee8e6749fc4 2.6.30 2.6.28
LinuxLinux	Affected =2.6.30	Fixed in–

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

References

Community reviews

Loading reviews…