CVE-2026-64370: Linux kernel · posix-cpu-timers: Fix pid refcount leak in do_cpu_nanosleep() error path
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in eb4cec29a78334d09bcfb41c0660cdd62ba05843 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 17:04 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- 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 eb4cec29a78334d09bcfb41c0660cdd62ba05843, e5ffc638faf5dc7d9dc85c9a95e10bf97442e0c0, d605d00085adc3fddf67de01dc2a44aebf1a3fb5 +5
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.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: Fix pid refcount leak in do_cpu_nanosleep() error path In do_cpu_nanosleep(), posix_cpu_timer_create() takes a pid reference via get_pid() and stores it in timer.it.cpu.pid. If the subsequent posix_cpu_timer_set() call fails, the function returns immediately without calling posix_cpu_timer_del() to release the pid reference, causing a leak. Fix it by calling posix_cpu_timer_del() before the unlock-and-return on the error path, consistent with the other exit paths in the same function.
References
- git.kernel.org/stable/c/afed3cdc1cca133f804fcf57ff228974f424b23a (opens in a new tab)
- git.kernel.org/stable/c/8a270b1258797f61b61da44f8bfd41a581b5c85b (opens in a new tab)
- git.kernel.org/stable/c/d605d00085adc3fddf67de01dc2a44aebf1a3fb5 (opens in a new tab)
- git.kernel.org/stable/c/e5ffc638faf5dc7d9dc85c9a95e10bf97442e0c0 (opens in a new tab)
- git.kernel.org/stable/c/eb4cec29a78334d09bcfb41c0660cdd62ba05843 (opens in a new tab)
- git.kernel.org/stable/c/7776f9226e99eb49d97492b0b445027cfcb189da (opens in a new tab)
- git.kernel.org/stable/c/8f06363446c5d043c9a7c008b250040e9de98cf9 (opens in a new tab)
- git.kernel.org/stable/c/87bd2ad568e15b90d5f7d4bcd70342d05dad649c (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-019113.html (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-457936.html (opens in a new tab)