<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-01T22:12:48.260325+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-54904</id>
    <title>CVE-2026-54904 — concurrent-ruby:  `AtomicReference#update` livelocks when the stored value is `Float::NAN`</title>
    <updated>2026-10-01T22:12:48.388411+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> ruby-concurrency concurrent-ruby</p>
<p>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 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.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-54904"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-h8w8-99g7-qmvj</id>
    <title>GHSA-h8w8-99g7-qmvj — Concurrent Ruby : `AtomicReference#update` livelocks when the stored value is `Float::NAN`</title>
    <updated>2026-10-01T22:12:48.388544+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> RubyGems: concurrent-ruby</p>
<p>### Summary
`Concurrent::AtomicReference#update` can enter a permanent busy retry loop when the current value is `Float::NAN`.</p>
<p>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.
- Ruby NaN semantics, where `Float::NAN == Float::NAN` is always `false`.</p>
<p>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.</p>
<p>### Version
Software: concurrent-ruby
Version: 1.3.6
Commit: 7a1b78941c081106c20a9ca0144ac73a48d254ab
### Details</p>
<p>`AtomicReference#update` retries until `compare_and_set` returns true:</p>
<p>```ruby
def update
  true until compare_and_set(old_value = get, new_value = yield(old_value))
  new_value
end
```</p>
<p>For numeric expected values, `compare_and_set` uses numeric equality before attempting the underlying atomic compare-and-set:</p>
<p>```ruby
def compare_and_set(old_value, new_value)
  if old_value.kind_of? Numeric
    while true
      old = get</p>
<p>return false unless old.kind_of? Numeric
      return false unless old == old_value</p>
<p>result = _compare_and_set(old, new_value)
      return result if result
    end
  else
    _compare_and_set(old_value,…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-h8w8-99g7-qmvj"/>
  </entry>
</feed>
