p PatchFirst

PatchFirst · Vulnerabilidades recientes

Vulnerabilidades de ruby-concurrent

Vulnerabilidades publicadas para ruby-concurrent en los últimos 30 días: 0. Incluidas en el catálogo KEV: 0.

Filtrar vulnerabilidades
Borrar filtros

Vulnerabilidades: 3

  1. CVE-2026-54906

    Baja · CVSS 2.1EPSS 0,16%Corrección disponible

    concurrent-ruby: ReadWriteLock allows wrong-thread write release and stray read-release counter corruption

    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 cor

    • Actualiza a 1.3.7-1
    Publicación Actualización
  2. CVE-2026-54904

    Alta · CVSS 8.2EPSS 0,67%Corrección disponible

    concurrent-ruby: `AtomicReference#update` livelocks when the stored value is `Float::NAN`

    concurrent-ruby is a modern concurrency tools for Ruby. Prior to 1.3.7, Concurrent::AtomicReference#update can enter a permanent busy retry loop when the current value is Float::NAN. The issue is caused by the interaction between AtomicReference#update, which retries until compare_and_set(old_value, new_value) succeeds; Numeric compare_and_set, which checks old == old_value before attempting the underlying atomic swap.; and Ruby NaN semantics, where Float::NAN == Float::NAN is always false. As a result, once an AtomicReference contains Float::NAN, calling #update repeatedly evaluates the caller's block and never returns. In services that stor

    • Actualiza a 1.3.7-1
    Publicación Actualización
  3. CVE-2026-54905

    Baja · CVSS 2EPSS 0,15%Corrección disponible

    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

    • Actualiza a 1.3.7-1
    Publicación Actualización

Comprueba tu servidor

Compara tu pila y las versiones instaladas con las bases actuales de vulnerabilidades.

Comprueba tu servidor →