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-2024-50210posix-clock: posix-clock: Fix unbalanced locking in pc_clock_settime()

Description

In the Linux kernel, the following vulnerability has been resolved: posix-clock: posix-clock: Fix unbalanced locking in pc_clock_settime() If get_clock_desc() succeeds, it calls fget() for the clockid's fd, and get the clk->rwsem read lock, so the error path should release the lock to make the lock balance and fput the clockid's fd to make the refcount balance and release the fd related resource. However the below commit left the error path locked behind resulting in unbalanced locking. Check timespec64_valid_strict() before get_clock_desc() to fix it, because the "ts" is not changed after that. [[email protected]: fixed commit message typo]

Timeline

  1. ID reserved

    By Linux

  2. · 18 days later

    Published

  3. · 24 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-2024-50210, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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.17% · top 94% 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 29f085345cde24566efb751f39e5d367c381c584 – < d005400262ddaf1ca1666bbcd1acf42fe81d57ce
    • affected e0c966bd3e31911b57ef76cec4c5796ebd88e512 – < a8219446b95a859488feaade674d13f9efacfa32
    • affected 673a1c5a2998acbd429d6286e6cad10f17f4f073 – < c7fcfdba35abc9f39b83080c2bce398dad13a943
    • affected c8789fbe2bbf75845e45302cba6ffa44e1884d01 – < e56e0ec1b79f5a6272c6e78b36e9d593aa0449af
    • affected 27abbde44b6e71ee3891de13e1a228aa7ce95bfe – < 5f063bbf1ee6b01611c016b54e050a41506eb794
    • affected a3f169e398215e71361774d13bf91a0101283ac2 – < 1ba33b327c3f88a7baee598979d73ab5b44d41cc
    • affected 1ff7247101af723731ea42ed565d54fb8f341264 – < b27330128eca25179637c1816d5a72d6cc408c66
    • affected d8794ac20a299b647ba9958f6d657051fc51a540 – < 6e62807c7fbb3c758d233018caf94dfea9c65dbd
  • Linux · Linux

    • affected 5.10.228 – < 5.10.229
    • affected 5.15.169 – < 5.15.170
    • affected 6.1.114 – < 6.1.115
    • affected 6.6.58 – < 6.6.59
    • affected 6.11.5 – < 6.11.6

References

References11

Sources

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

Badge for a README or a ticket

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

Record last updated .