Read the docs

Use-after-free in Valkey RDMA handler allows server crashes

Priority MEDIUM 48CWE-416Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
High
Impact type
Code execution
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 3.1 · GHSA-jcj7-v34w-v9vv. Fix status from GitHub. Impact type from CWE-416 and the CVSS impact.

Summary

Valkey server builds with RDMA support free a client connection while the RDMA pending-data handler still uses it, a use-after-free (CWE-416). Affected versions are up to and including 9.1.1, 9.0.5, 8.1.9 and 8.0.10. An authenticated user with low privileges can trigger it with a command such as CLIENT KILL, crashing the server. Only servers built with USE_RDMA and configured with an RDMA listener are affected.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Description from the GitHub advisory

## Impact An authenticated user can run a command that frees another client's connection while the RDMA transport is processing pending data, leaving a dangling pointer that is dereferenced shortly after. This reliably crashes the server process, and the freed heap chunk can be reclaimed with attacker-influenced bytes. This issue only affects servers built with RDMA support (`USE_RDMA`) and configured with an RDMA listener, which is off by default and requires RDMA-capable hardware. Builds without RDMA are not affected, and the RDMA transport does not exist before 8.0. ## Details The RDMA pending-data handler walked its connection list with an iterator that caches the next entry. Running a client's read handler from inside that loop can process a command such as `CLIENT KILL`, which synchronously frees a different client's connection, invalidating the cached entry. Separately, closing an RDMA connection freed it without removing it from the pending list, so a stale entry also persisted into later passes. This is the RDMA equivalent of the TLS issue fixed in GHSA-53mc-f3m3-99vh. ## Mitigation If you do not need RDMA, build without `USE_RDMA` or do not configure an RDMA listener. Otherwise, you can mitigate this issue by using Valkey ACLs to restrict the CLIENT command, in particular `CLIENT KILL`. ## Credits Reported by Andreas Gabriel Berbescu ([email protected]

Why it matters now

Fix Fixed valkey-server: 9.1.2, 9.0.6, 8.1.10 +1

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—valkey-server<= 9.1.1, <= 9.0.5, <= 8.1.9, <= 8.0.109.1.2, 9.0.6, 8.1.10, 8.0.11Patch availableGHSA-jcj7-v34w-v9vv
  • valkey-server Vendor— Affected <= 9.1.1, <= 9.0.5, <= 8.1.9, <= 8.0.10 Fixed in 9.1.2, 9.0.6, 8.1.10, 8.0.11 Patch available GHSA-jcj7-v34w-v9vv

Remediation

Upgrade valkey-server to 9.1.2, 9.0.6, 8.1.10 or 8.0.11, matching your release branch. Until you upgrade, build without USE_RDMA or do not configure an RDMA listener, or restrict the CLIENT command, in particular CLIENT KILL, with Valkey ACLs.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

  • Fix · GHSA-jcj7-v34w-v9vv valkey-server Fixed in 9.1.2, 9.0.6, 8.1.10, 8.0.11 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-jcj7-v34w-v9vv

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences