This page tracks the Debian fix status. The vulnerability itself is described on the main CVE page. View CVE-2026-54905 →
Categories
DEBIAN-CVE-2026-54905

concurrent-ruby is a modern concurrency tools for Ruby. Prior to 1.3.7, Concurrent::ReentrantReadWriteLock can incorrectly grant a write lock after on...

Original description

The description as published by the source.

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.

Source: OSV.dev (Open Source Vulnerabilities) OSV

Affected packages

Debian:12 ruby-concurrent
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Debian:13 ruby-concurrent
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Debian:14 ruby-concurrent
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.3.7-1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details