Skip to main content
VulnerabilityPublished Updated

CVE-2026-64370: Linux kernel · posix-cpu-timers: Fix pid refcount leak in do_cpu_nanosleep() error path

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in eb4cec29a78334d09bcfb41c0660cdd62ba05843 : 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
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

  1. Disclosed: evidence found.

    CVE published 25 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < eb4cec29a78334d09bcfb41c0660cdd62ba05843
Fixed in
  • eb4cec29a78334d09bcfb41c0660cdd62ba05843
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < e5ffc638faf5dc7d9dc85c9a95e10bf97442e0c0
Fixed in
  • e5ffc638faf5dc7d9dc85c9a95e10bf97442e0c0
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < d605d00085adc3fddf67de01dc2a44aebf1a3fb5
Fixed in
  • d605d00085adc3fddf67de01dc2a44aebf1a3fb5
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < afed3cdc1cca133f804fcf57ff228974f424b23a
Fixed in
  • afed3cdc1cca133f804fcf57ff228974f424b23a
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 7776f9226e99eb49d97492b0b445027cfcb189da
Fixed in
  • 7776f9226e99eb49d97492b0b445027cfcb189da
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 87bd2ad568e15b90d5f7d4bcd70342d05dad649c
Fixed in
  • 87bd2ad568e15b90d5f7d4bcd70342d05dad649c

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

Community reviews

Loading reviews…