All vulnerabilities

Servers and applications

GHSA-jcj7-v34w-v9vv

Use-after-free in the RDMA pending-data handler when a client

Severity
High 7.5
Published
31 Aug 2026
Last changed
31 Aug 2026
Added to UpHeron
3 Nov 2026
Fixed in
8.0.11
Weakness
Use after free (CWE-416)
Attack
Over the network · Only under certain conditions · Needs a user account · No user action needed
Attacker can
Read data · Change data · Take it down
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Sources
Project advisories (GitHub)

Description

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.

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.

From valkey-io/valkey's security advisory. Shortened; the full text is there.

Workarounds

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.

Workarounds as given by valkey-io/valkey's security advisory.

Affected software

SoftwareAffected versions
ValkeyServers and applications · github:valkey-io/valkey
  • Every version before 8.0.11

About Valkey

NoSQL database management software forked from Redis

From Wikidata, CC0 1.0.
Developers who used it in the past year
2.4%Stack Overflow Developer Survey 2025, 2025
Docker Hub pulls
404,291,684Docker Hub, 15 Nov 2026
GitHub stars
27,721GitHub, 15 Nov 2026
Forks
1,535GitHub, 15 Nov 2026
Latest release
9.1.3GitHub, 15 Nov 2026
Released
26 Oct 2026GitHub
License
3-clause BSD LicenseWikidata
Written in
CWikidata
First released
28 Mar 2024Wikidata
First published on GitHub
22 Mar 2024GitHub

Release lines

ReleaseLatestSecurity fixes
9.19.1.3Until 19 May 2031
9.09.0.7Until 21 Oct 2028
8.18.1.11Until 31 Mar 2030
8.08.0.12Until 15 Sept 2027
7.27.2.15Until 16 Apr 2029

From endoflife.date.

References