CVE-2026-64370

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.

Is your site exposed to CVE-2026-64370?

Run a free security scan — no signup, results in seconds.

EPSS — Exploit Prediction

0.0022

Probability of exploitation

0.13%

Percentile rank

EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.

References

Other References

https://git.kernel.org/stable/c/7776f9226e99eb49d97492b0b445027cfcb189da https://git.kernel.org/stable/c/87bd2ad568e15b90d5f7d4bcd70342d05dad649c https://git.kernel.org/stable/c/8a270b1258797f61b61da44f8bfd41a581b5c85b https://git.kernel.org/stable/c/8f06363446c5d043c9a7c008b250040e9de98cf9 https://git.kernel.org/stable/c/afed3cdc1cca133f804fcf57ff228974f424b23a https://git.kernel.org/stable/c/d605d00085adc3fddf67de01dc2a44aebf1a3fb5 https://git.kernel.org/stable/c/e5ffc638faf5dc7d9dc85c9a95e10bf97442e0c0 https://git.kernel.org/stable/c/eb4cec29a78334d09bcfb41c0660cdd62ba05843

Frequently Asked Questions

What is CVE-2026-64370? +

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.

How do I check if I'm vulnerable to CVE-2026-64370? +

You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.