Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-64370, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < afed3cdc1cca133f804fcf57ff228974f424b23a
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 8a270b1258797f61b61da44f8bfd41a581b5c85b
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < d605d00085adc3fddf67de01dc2a44aebf1a3fb5
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < e5ffc638faf5dc7d9dc85c9a95e10bf97442e0c0
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < eb4cec29a78334d09bcfb41c0660cdd62ba05843
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 7776f9226e99eb49d97492b0b445027cfcb189da
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 8f06363446c5d043c9a7c008b250040e9de98cf9
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 87bd2ad568e15b90d5f7d4bcd70342d05dad649c
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.96 – ≤ 6.12.*
    • unaffected 6.18.39 – ≤ 6.18.*
    • unaffected 7.1.4 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64370 badge
[![CVE-2026-64370](https://cveledger.app/badge/CVE-2026-64370.svg)](https://cveledger.app/cve/CVE-2026-64370)

Record last updated .