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

concurrent-ruby is a modern concurrency tools for Ruby. Prior to 1.3.7, Concurrent::ReadWriteLock#release_write_lock does not verify that the calling...

Original description

The description as published by the source.

concurrent-ruby is a modern concurrency tools for Ruby. Prior to 1.3.7, Concurrent::ReadWriteLock#release_write_lock does not verify that the calling thread acquired the write lock. Any thread with access to the lock object can release an active write lock held by another thread. A second writer can then enter its critical section while the first writer is still running. Concurrent::ReadWriteLock#release_read_lock also decrements the shared counter even when no read lock is held. Calling it on a fresh lock changes the counter from 0 to -1, after which normal read acquisition raises Concurrent::ResourceLimitError. This is a synchronization correctness issue in the public Concurrent::ReadWriteLock API. 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