Nonexclusive write lock via read-count bit overflow
Published Jun 24, 2026 · Updated Jun 24, 2026
Wrap-around in Concurrent::ReentrantReadWriteLock in ruby-concurrency concurrent-ruby before 1.3.7 allows local users to bypass write exclusivity. The per-thread held count shares its low 15 read-count bits with the WRITE_LOCK_HELD bit, so 32,768 reentrant reads make try_write_lock return true without setting RUNNING_WRITER. The calling thread needs access to the lock object and extreme reentrant read depth; concurrent readers can then race with supposedly exclusive writes and observe inconsistent protected state.
Summary
What happened
Wrap-around in Concurrent::ReentrantReadWriteLock in ruby-concurrency concurrent-ruby before 1.3.7 allows local users to bypass write exclusivity. The per-thread held count shares its low 15 read-count bits with the WRITE_LOCK_HELD bit, so 32,768 reentrant reads make try_write_lock return true without setting RUNNING_WRITER. The calling thread needs access to the lock object and extreme reentrant read depth; concurrent readers can then race with supposedly exclusive writes and observe inconsistent protected state.
The record
- CVE
- CVE-2026-54905
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- ruby-concurrency
- Product
- concurrent-ruby
- Classifications
- CWE-128
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 24, 2026CVE publishedPublication date reported by the CVE source.
- Jun 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.3.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream ReentrantReadWriteLock reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo