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-2023-53728posix-timers: Ensure timer ID search-loop limit is valid

Description

In the Linux kernel, the following vulnerability has been resolved: posix-timers: Ensure timer ID search-loop limit is valid posix_timer_add() tries to allocate a posix timer ID by starting from the cached ID which was stored by the last successful allocation. This is done in a loop searching the ID space for a free slot one by one. The loop has to terminate when the search wrapped around to the starting point. But that's racy vs. establishing the starting point. That is read out lockless, which leads to the following problem: CPU0 CPU1 posix_timer_add() start = sig->posix_timer_id; lock(hash_lock); ... posix_timer_add() if (++sig->posix_timer_id < 0) start = sig->posix_timer_id; sig->posix_timer_id = 0; So CPU1 can observe a negative start value, i.e. -1, and the loop break never happens because the condition can never be true: if (sig->posix_timer_id == start) break; While this is unlikely to ever turn into an endless loop as the ID space is huge (INT_MAX), the racy read of the start value caught the attention of KCSAN and Dmitry unearthed that incorrectness. Rewrite it so that all id operations are under the hash lock.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 7 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (15 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 5ed67f05f66c41e39880a6d61358438a25f9fee5 – < 8dc52c200b889bc1cb34288fbf623d4ff381d2ae
    • affected 5ed67f05f66c41e39880a6d61358438a25f9fee5 – < 9ea26a8494a0a9337e7415eafd6f3ed940327dc5
    • affected 5ed67f05f66c41e39880a6d61358438a25f9fee5 – < 8ad6679a5bb97cdb3e14942729292b4bfcc0e223
    • affected 5ed67f05f66c41e39880a6d61358438a25f9fee5 – < 322377cc909defcca9451487484845e7e1d20d1b
    • affected 5ed67f05f66c41e39880a6d61358438a25f9fee5 – < ef535e0315afd098c4beb1da364847eca4b56a20
    • affected 5ed67f05f66c41e39880a6d61358438a25f9fee5 – < 6a0ac84501b4fec73a1a823c55cf13584c43f418
    • affected 5ed67f05f66c41e39880a6d61358438a25f9fee5 – < 37175e25edf7cc0d5a2cd2c2a1cbe2dcbf4a1937
    • affected 5ed67f05f66c41e39880a6d61358438a25f9fee5 – < 8ce8849dd1e78dadcee0ec9acbd259d239b7069f
  • Linux · Linux

    • affected 3.10
    • unaffected < 3.10
    • unaffected 4.14.322 – ≤ 4.14.*
    • unaffected 4.19.291 – ≤ 4.19.*
    • unaffected 5.4.251 – ≤ 5.4.*
    • unaffected 5.10.188 – ≤ 5.10.*
    • unaffected 5.15.150 – ≤ 5.15.*
    • unaffected 6.1.107 – ≤ 6.1.*
    • unaffected 6.4.7 – ≤ 6.4.*
    • unaffected 6.5 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .