CVE-2026-54905
- Source
- https://cve.org/CVERecord?id=CVE-2026-54905
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-54905.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2026-54905
- Aliases
- Downstream
- Published
- 2026-06-24T15:42:44Z
- Modified
- 2026-08-12T03:30:13Z
- Severity
-
- 2.0 (Low) CVSS_V4 - CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N CVSS Calculator
- Summary
- concurrent-ruby: `ReentrantReadWriteLock` read-count overflow grants a write lock without exclusivity
- Details
-
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.
- Database specific
{ "cna_assigner": "GitHub_M", "cwe_ids": [ "CWE-128" ], "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/54xxx/CVE-2026-54905.json" }- References
Affected packages
Git / github.com/ruby-concurrency/concurrent-ruby
Affected ranges
- Type
- GIT
- Repo
- https://github.com/ruby-concurrency/concurrent-ruby
- Events
-
Introduced0 Unknown introduced commit / All previous commits are affectedFixed
- Database specific
-
Show details
{ "cpe": "cpe:2.3:a:rubyconcurrency:concurrent_ruby:*:*:*:*:*:ruby:*:*", "extracted_events": [ { "introduced": "0" }, { "fixed": "1.3.7" } ], "source": [ "AFFECTED_FIELD", "CPE_RANGE" ] }