CVE-2026-98257 json
rds: ib: use rds_conn_drop() on protocol version mismatch
published last mo. modified 24d ago also EUVD-2026-93185
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 7.3
- linux Debian 12 6.1.190-1
- linux Debian 13 6.12.113-1
- linux Debian 14 7.2.8-1
- linux-6.12 Debian 12 6.12.113-1~deb12u1
debian advisories DEBIAN-CVE-2026-98257
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 24.04 LTS 6.8.0-149.149
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 24.04 LTS 6.8.0-1069.74
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1073.81
ubuntu advisories UBUNTU-CVE-2026-98257
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source Linux Micro 6.0 6.4.0-159998.55.1
- kernel-default Linux Micro 6.0 6.4.0-159998.55.1
- kernel-kvmsmall Linux Micro 6.0 6.4.0-159998.55.1
- kernel-default-base Linux Micro 6.0 6.4.0-159998.55.1.159998.21.42
- kernel-syms SLES LTSS Extended Security 12 SP5, SLES 12 SP5-LTSS 4.12.14-122.339.1
- kernel-source SLES LTSS Extended Security 12 SP5, SLES 12 SP5-LTSS 4.12.14-122.339.1
- kernel-default SLES LTSS Extended Security 12 SP5, SLES 12 SP5-LTSS, SLE Live Patching 12 SP5 4.12.14-122.339.1
- kgraft-patch-SLE12-SP5_Update_90 SLE Live Patching 12 SP5 1-8.3.1
suse advisories SUSE-SU-2026:5121-1SUSE-SU-2026:24550-1
- kernel-source openSUSE Tumbleweed 7.2.10-1.1
opensuse advisories openSUSE-SU-2026:12131-1
- kernel Azure Linux 3.0 6.6.158.1-1
azure linux advisories AZL-106431
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/424019be3f637da76b74f44a40034669acbb166f commit
- git.kernel.org/stable/c/14fb90067d13f4494cff0f03243fae3cf2911cbc commit
- git.kernel.org/stable/c/344c72a0bc2703a6de4918ed935850e07dae3af2 commit
- git.kernel.org/stable/c/b5c9f2951d330d4a198a64d6e60f79b4bd6ef078 commit
- git.kernel.org/stable/c/d392b16acd0908f077289aad8bba066ff16de336 commit
- git.kernel.org/stable/c/65ca0a5037152a5a80b8fe6aac80eb80458be573 commit
- git.kernel.org/stable/c/7d8c22cb2cb1efb5e830a4545c76abf7b35cc2e8 commit
- git.kernel.org/stable/c/f97d8c7bab7843631206a114986c9059da03efeb commit
Is CVE-2026-98257 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.50% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/424019be3f637da76b74f44a40034669acbb166f
- git.kernel.org /stable/c/14fb90067d13f4494cff0f03243fae3cf2911cbc
- git.kernel.org /stable/c/344c72a0bc2703a6de4918ed935850e07dae3af2
- git.kernel.org /stable/c/b5c9f2951d330d4a198a64d6e60f79b4bd6ef078
- git.kernel.org /stable/c/d392b16acd0908f077289aad8bba066ff16de336
- git.kernel.org /stable/c/65ca0a5037152a5a80b8fe6aac80eb80458be573
- git.kernel.org /stable/c/7d8c22cb2cb1efb5e830a4545c76abf7b35cc2e8
- git.kernel.org /stable/c/f97d8c7bab7843631206a114986c9059da03efeb
Sources
- CVE List CVE-2026-98257
- NVD CVE-2026-98257
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.