memtomem/memtomem-stm · Security
memtomem-stm: Concurrent LTM recovery can duplicate reconnects or reuse a cancelled transport session
- GHSA ID
- GHSA-72jh-722p-rqr3
- CVE ID
- CVE-2026-77331
- Severity
- low
- Published
- Updated
- CVSS v4
- 2 · CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:L
Description
Concurrent surfacing RPC failures can trigger more than one reconnect for the same dirty session, and cancellation during a post-reconnect retry can leave the replacement session reusable despite an interrupted protocol exchange. The private fix introduces monotonic session generations, one shielded shared reconnect flight per dirty generation, and generation-aware cancellation handling across search, access-count, and scratch RPCs. The duplicate-reconnect subcase was introduced in 0.1.24; cancellation recovery affects the broader listed range.
CWEs
- CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization
References
- https://github.com/memtomem/memtomem-stm/security/advisories/GHSA-72jh-722p-rqr3 ↗
- https://nvd.nist.gov/vuln/detail/CVE-2026-77331 ↗
- https://github.com/memtomem/memtomem-stm/commit/761db1802df7ce4881ff4c3acee6d674925da498 ↗
- https://github.com/memtomem/memtomem-stm/releases/tag/v0.1.34 ↗
- https://github.com/advisories/GHSA-72jh-722p-rqr3 ↗