Skip to content
Heist/ feed
UnratedFix available

xprtrdma: Initialize re_id before removal registration

Type: advisorySource: OSV1 source record

In the Linux kernel, the following vulnerability has been resolved: xprtrdma: Initialize re_id before removal registration rpcrdma_create_id() registers ep->re_rn with the rpcrdma ib_client before returning the new rdma_cm_id to rpcrdma_ep_create(). However rpcrdma_ep_create() currently stores that pointer in ep->re_id only after rpcrdma_create_id() returns. A local administrator can race an NFS/RDMA mount against RDMA device removal. If rpcrdma_remove_one() observes the just-registered notification before rpcrdma_ep_create() assigns ep->re_id, rpcrdma_ep_removal_done() calls trace_xprtrdma_device_removal(NULL). The tracepoint dereferences id->device->name and copies id->route.addr.dst_addr, so the callback can crash the kernel with a NULL pointer dereference. Store the rdma_cm_id in ep->re_id immediately before publishing ep->re_rn. The existing error path still destroys the id directly if registration fails; ep is then freed by the caller without using ep->re_id. Remove the later duplicate assignment in rpcrdma_ep_create().

Announced Source revision 1
Original source ↗

CVE-2026-72468

Primary source · Revision 1

Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.

Security context

Source reference: osv:CVE-2026-72468

Kernel

Source reference: /affected/1/package/name

Affected versions
Not stated in this record
Fixed versions
6.12.97

Source reference: /affected/1/ranges

6.18.40

Source reference: /affected/1/ranges

7.1.5

Source reference: /affected/1/ranges

Prerequisites
Not stated in this record

Structured affected-version data

Original package identities and version rules from this source.

[
  {
    "ranges": [
      {
        "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
        "type": "GIT",
        "events": [
          {
            "introduced": "3f4eb9ff923413cdb4c7e171c06d3564f6286712"
          },
          {
            "fixed": "51248d877bbc6e604e38aeaf776c2781cb4f0dbd"
          },
          {
            "fixed": "28743571c17b58c21a7216fc9faaf8028df5869b"
          },
          {
            "fixed": "264ccd7871915749bee55fe0c39467a7f08d5479"
          },
          {
            "fixed": "bb7caa63e1db22fd03e8dc591b12169e99169dff"
          }
        ]
      }
    ],
    "database_specific": {
      "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-72468.json"
    }
  },
  {
    "ranges": [
      {
        "type": "ECOSYSTEM",
        "events": [
          {
            "introduced": "6.11.0"
          },
          {
            "fixed": "6.12.97"
          }
        ]
      },
      {
        "type": "ECOSYSTEM",
        "events": [
          {
            "introduced": "6.13.0"
          },
          {
            "fixed": "6.18.40"
          }
        ]
      },
      {
        "type": "ECOSYSTEM",
        "events": [
          {
            "introduced": "6.19.0"
          },
          {
            "fixed": "7.1.5"
          }
        ]
      }
    ],
    "package": {
      "name": "Kernel",
      "ecosystem": "Linux"
    },
    "database_specific": {
      "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-72468.json"
    }
  }
]
Related CVEs
CVE-2026-72468

Source reference: /id

Publisher severity

No explicit severity was provided.

Event
#50768 · Revision 1
Added to Heist Feed
Publisher date
Read the original announcement