ZDF
Sign inSign up

Vulnerabilities

Security fix · GHSA-jcj7-v34w-v9vv

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

Published Aug 31, 2026 · catalog updated Aug 31, 2026 · Use-after-free in the RDMA

Last checked Nov 1, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for GHSA-jcj7-v34w-v9vv. A missing EPSS score is not a low risk. Compare Use-after-free in the RDMA with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Use-after-free in the RDMA).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Not established
Affected products
See sources for product scope

## 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 ( ) 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 , 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 or do not configure an RDMA listener. Otherwise, you can mitigate this issue by using Valkey ACLs to restrict the CLIENT command, in particular . ## Credits Reported by Andreas Gabriel Berbescu (aberbescu@gmail.com

No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.

How to fix GHSA-jcj7-v34w-v9vv

  • No stored fix

    No vendor fix text is stored. Use the linked advisory before you change production.

  • Version check

    No version range is stored, so an installed version cannot be checked on this page.

  • Advisory

    Open the inventory_github record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for GHSA-jcj7-v34w-v9vv. A missing EPSS score is not a low risk. Compare Use-after-free in the RDMA with the linked advisory before you change production.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-416: Use After Free. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Valkey security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Aug 31, 2026 · Maintainer security tabs

    Detected

    ## 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 ( ) and configured with

Sources

  • Maintainer security tabsVendor advisoryGHSA-jcj7-v34w-v9vv

    ## 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 ( ) and configured with

    github.com

Freshness

Last verified in this catalog Aug 31, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Maintainer security tabsNov 1, 2026