CVE-2026-98257
rds: ib: use rds_conn_drop() on protocol version mismatch
No known exploitation. EPSS puts it in the 43rd percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ f147dd9ecabf23fd63d2562ffe64252a0453ecde, < 424019be3f637da76b74f44a40034669acbb166fUpgrade to: 424019be3f637da76b74f44a40034669acbb166fAffected: ≥ f147dd9ecabf23fd63d2562ffe64252a0453ecde, < 14fb90067d13f4494cff0f03243fae3cf2911cbcUpgrade to: 14fb90067d13f4494cff0f03243fae3cf2911cbcAffected: ≥ f147dd9ecabf23fd63d2562ffe64252a0453ecde, < 344c72a0bc2703a6de4918ed935850e07dae3af2Upgrade to: 344c72a0bc2703a6de4918ed935850e07dae3af2Affected: ≥ f147dd9ecabf23fd63d2562ffe64252a0453ecde, < b5c9f2951d330d4a198a64d6e60f79b4bd6ef078Upgrade to: b5c9f2951d330d4a198a64d6e60f79b4bd6ef078 + 4 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
In the Linux kernel, the following vulnerability has been resolved: rds: ib: use rds_conn_drop() on protocol version mismatch rds_ib_cm_connect_complete() runs from the RDMA-CM event handler with conn->c_cm_lock held. When the peer negotiates a protocol version older than RDS_PROTOCOL_COMPAT_VERSION, the handler calls rds_conn_destroy(), which is only safe in the rmmod path: it synchronously tears the connection down and flush_work()es the shutdown work cp_down_w. That shutdown work (rds_conn_shutdown()) needs cp_cm_lock, which is the very lock the event handler still holds, so the flush never completes: the two workers wait on each other and the RDS connection workqueues stall for good. All other RDMA-CM failure paths (REJECTED, CONNECT_ERROR, DISCONNECTED) use rds_conn_drop(), which marks the connection RDS_CONN_ERROR and schedules the shutdown work asynchronously. Use it here as well.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.5% chance of exploitation activity in the next 30 days, which ranks it in the 43rd percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
3 events over 1 day, from the signal feeds we watch.
- Record updated
- Publishedrecord updated
Affected products
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Scored 7.5 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality NoneNo confidentiality impact
- Integrity NoneNo integrity impact
- Availability HighTotal denial of service — the component is completely unavailable
Sources
References in the record
- git.kernel.org/stable/c/14fb90067d13f4494cff0f03243fae3cf2911cbc
- git.kernel.org/stable/c/344c72a0bc2703a6de4918ed935850e07dae3af2
- git.kernel.org/stable/c/424019be3f637da76b74f44a40034669acbb166f
And 5 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI