CVE-2026-54905
concurrent-ruby: `ReentrantReadWriteLock` read-count overflow grants a write lock without exclusivity
concurrent-ruby is a modern concurrency tools for Ruby. Prior to 1.3.7, Concurrent::ReentrantReadWriteLock can incorrectly grant a write lock after one thread acquires the read lock 32,768 times. The lock stores a thread's local read and write hold counts in one integer. The low 15 bits are used for the read hold count, and bit 15 is used as WRITE_LOCK_HELD. After 32,768 reentrant read acquisitions, the local read count crosses into the write-lock bit. try_write_lock then treats the thread as already holding a write lock and returns true without setting the global RUNNING_WRITER bit. This breaks the core mutual-exclusion guarantee: the caller is told it has a write lock, but other threads can still hold or acquire read locks at the same time. This vulnerability is fixed in 1.3.7.
| CWE | CWE-128 |
| Vendor | ruby-concurrency |
| Product | concurrent-ruby |
| Published | Jun 24, 2026 |
| Last Updated | Jun 24, 2026 |
Get instant alerts for ruby-concurrency concurrent-ruby
Be the first to know when new unknown vulnerabilities affecting ruby-concurrency concurrent-ruby are published โ delivered to Slack, Telegram or Discord.