Skip to main content
CVE-2026-64370VulnerabilityPublished 07/25/2026Updated 09/08/2026

In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: Fix pid refcount leak in do_cpu_nanosleep() error path In… (CVE-2026-64370)

Source GCVE Database

0
Severity
Medium

No CVSS score published yet

Exploitation

Not in CISA KEV, no exploitation reported

EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

What to do

AI-suggested

A fix has been implemented in the Linux kernel to properly release the pid reference on the error path in do_cpu_nanosleep(). Users should apply the official kernel update or patch that includes this fix once available. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor or kernel mailing list advisories for the current remediation guidance.

Description

A vulnerability in the Linux kernel's posix-cpu-timers subsystem caused a pid reference count leak in the do_cpu_nanosleep() error path. Specifically, if posix_cpu_timer_set() fails after a pid reference is taken, the reference is not released, leading to a resource leak. This issue has been resolved by ensuring the pid reference is properly released on error paths.

Impact

The vulnerability causes a pid reference count leak in the kernel, which could lead to resource exhaustion or instability over time if the error path is triggered repeatedly. There is no indication of direct privilege escalation or code execution impact. No known exploits in the wild have been reported.

Summary

The Linux kernel's posix-cpu-timers code in do_cpu_nanosleep() takes a pid reference via get_pid() and stores it in timer.it.cpu.pid. If the subsequent call to posix_cpu_timer_set() fails, the function previously returned immediately without releasing the pid reference by calling posix_cpu_timer_del(), causing a reference count leak. The fix involves calling posix_cpu_timer_del() before returning on the error path, aligning with other exit paths in the function to prevent the leak.

References

Community reviews

Loading reviews…