CVE-2026-31425
rds: ib: reject FRMR registration before IB connection is established
Reported by linux · Published April 13, 2026
In the Linux kernel, the following vulnerability has been resolved: rds: ib: reject FRMR registration before IB connection is established rds_ib_get_mr() extracts the rds_ib_connection from conn->c_transport_data and passes it to rds_ib_reg_frmr() for FRWR memory registration. On a fresh outgoing connection, ic is allocated in rds_ib_conn_alloc() with i_cm_id = NULL because the connection worker has not yet called rds_ib_conn_path_connect() to create the rdma_cm_id. When sendmsg() with RDS_CMSG_RDMA_MAP is called on such a connection, the sendmsg path parses the control message before any connection establishment, allowing rds_ib_post_reg_frmr() to dereference ic->i_cm_id->qp and crash the kernel. The existing guard in rds_ib_reg_frmr() only checks for !ic (added in commit 9e630bcb7701), which does not catch this case since ic is allocated early and is always non-NULL once the connection object exists. KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017] RIP: 0010:rds_ib_post_reg_frmr+0x50e/0x920 Call Trace: rds_ib_post_reg_frmr (net/rds/ib_frmr.c:167) rds_ib_map_frmr (net/rds/ib_frmr.c:252) rds_ib_reg_frmr (net/rds/ib_frmr.c:430) rds_ib_get_mr (net/rds/ib_rdma.c:615) __rds_rdma_map (net/rds/rdma.c:295) rds_cmsg_rdma_map (net/rds/rdma.c:860) rds_sendmsg (net/rds/send.c:1363) ____sys_sendmsg do_syscall_64 Add a check in rds_ib_get_mr() that verifies ic, i_cm_id, and qp are all non-NULL before proceeding with FRMR registration, mirroring the guard already present in rds_ib_post_inv(). Return -ENODEV when the connection is not ready, which the existing error handling in rds_cmsg_send() converts to -EAGAIN for userspace retry and triggers rds_conn_connect_if_down() to start the connection worker.
EPSS 0.11% · 1.5th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| Linux | Linux | a5bfd14c9a299e6db4add4440430ee5e010b03ad, a54ecccfae62c5c85259ae5ea5d9c20009519049, 6b0a8de67ac0c74e1a7df92b73c862cb36780dfc, 47de5b73db3b88f45c107393f26aeba26e9e8fae, 450ec93c0f172374acbf236f1f5f02d53650aa2d, 23e07c340c445f0ebff7757ba15434cb447eb662 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 1659185fb4d0025835eb2058a141f0746c5cab00, 1659185fb4d0025835eb2058a141f0746c5cab00, 1659185fb4d0025835eb2058a141f0746c5cab00 |
| Linux | Linux | 4.6, 0, 5.10.253 |
| linux | linux_kernel | 4.6, 4.6, 4.6 |
| Linux | Linux | 1659185fb4d0025835eb2058a141f0746c5cab00, 1659185fb4d0025835eb2058a141f0746c5cab00, 1659185fb4d0025835eb2058a141f0746c5cab00 |
Timeline
- Apr 13, 2026 CVE Published
- Apr 13, 2026 Security Advisory (78 in total, the first dated here)
- May 18, 2026 EPSS Score (22 in total, the first dated here)
- Jun 17, 2026 CVE Updated
- Jun 30, 2026 Coalition ESS Score
- Aug 11, 2026 Distribution Patch (75 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-31425
vulnetix vdb fixes CVE-2026-31425
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-31425/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart