CVE-2026-54904
- Source
- https://cve.org/CVERecord?id=CVE-2026-54904
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-54904.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-54904
- Aliases
- Downstream
- Related
- Published
- 2026-06-24T15:44:21.992Z
- Modified
- 2026-07-08T08:13:42.561920691Z
- Severity
-
- 8.2 (High) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N CVSS Calculator
- Summary
- concurrent-ruby: `AtomicReference#update` livelocks when the stored value is `Float::NAN`
- Details
-
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 compareandset(oldvalue, newvalue) succeeds; Numeric compareandset, 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 store externally derived numeric values in an AtomicReference, this can cause CPU exhaustion or permanent request/job hangs. This vulnerability is fixed in 1.3.7.
- Database specific
{ "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/54xxx/CVE-2026-54904.json", "cwe_ids": [ "CWE-835" ], "cna_assigner": "GitHub_M" }- 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
{ "cpe": "cpe:2.3:a:rubyconcurrency:concurrent_ruby:*:*:*:*:*:ruby:*:*", "source": [ "AFFECTED_FIELD", "CPE_RANGE" ], "extracted_events": [ { "introduced": "0" }, { "fixed": "1.3.7" } ] }