CVE-2026-98257

HIGHCVSS 7.5/10EPSS 0.18%

Last modified

CVE-2026-98257 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. 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. EPSS estimates a 0.18% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
0.18%

7.3th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= f147dd9ecabf23fd63d2562ffe64252a0453ecde, < 424019be3f637da76b74f44a40034669acbb166f; >= f147dd9ecabf23fd63d2562ffe64252a0453ecde, < 14fb90067d13f4494cff0f03243fae3cf2911cbc; >= f147dd9ecabf23fd63d2562ffe64252a0453ecde, < 344c72a0bc2703a6de4918ed935850e07dae3af2; >= f147dd9ecabf23fd63d2562ffe64252a0453ecde, < b5c9f2951d330d4a198a64d6e60f79b4bd6ef078; >= f147dd9ecabf23fd63d2562ffe64252a0453ecde, < d392b16acd0908f077289aad8bba066ff16de336; >= f147dd9ecabf23fd63d2562ffe64252a0453ecde, < 65ca0a5037152a5a80b8fe6aac80eb80458be573; >= f147dd9ecabf23fd63d2562ffe64252a0453ecde, < 7d8c22cb2cb1efb5e830a4545c76abf7b35cc2e8; >= f147dd9ecabf23fd63d2562ffe64252a0453ecde, < f97d8c7bab7843631206a114986c9059da03efeb
LinuxLinux2.6.37

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-98257?
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.
How severe is CVE-2026-98257?
CVE-2026-98257 has a CVSS score of 7.5/10 (HIGH severity). The EPSS model estimates a 0.18% probability of exploitation in the next 30 days.
How do I fix CVE-2026-98257?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-98257?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST