All vulnerabilities
CVE-2026-98072

Linux: net/rds: use wq_has_sleeper() in release_in_xmit()

Linux LinuxOperating systems
Open in ThreatlineRecord JSON
CVSS
NoneNot scored
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.18%Chance of exploitation activity in the next 30 days, higher than 6% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in6f552364d97cf4005c7a58f11c9f79e14e269865Also 5a806ed1eb46850ca4159a18b2a8c4b70f0c1341, 3d401934b7edb3ccb07d982dabadd04c45ee307c and 10 moreCVE List
Published25 Sep 2026Updated 19 Oct 2026CVE List

What fixes it

  • 6f552364d97cf4005c7a58f11c9f79e14e269865LinuxCVE List
  • 5a806ed1eb46850ca4159a18b2a8c4b70f0c1341LinuxCVE List
  • 3d401934b7edb3ccb07d982dabadd04c45ee307cLinuxCVE List
  • 3764627b30a283e611e652c4a2bb8cdc74a75a99LinuxCVE List
  • 6d0c8b7073913011459cf968cbbadd341e166bc3LinuxCVE List
  • 5.10.271LinuxCVE List
Show all 13 fixed versions

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

Description

In the Linux kernel, the following vulnerability has been resolved:

net/rds: use wq_has_sleeper() in release_in_xmit()

release_in_xmit() clears RDS_IN_XMIT with clear_bit_unlock() and then checks waitqueue_active() to decide whether anyone needs waking. clear_bit_unlock() is only a release operation: it orders the critical section before the bit clear, but does not order the subsequent plain load of the wait queue head after it. The waiter side does the mirror image - it adds itself to the wait queue and then tests the bit. That is the classic store-buffering pattern: the releasing CPU can read the wait queue as empty while the waiting CPU still reads the bit as set, so the sleeper is never woken.

The waiters are rds_conn_shutdown() and rds_tcp_reset_callbacks(), both in uninterruptible wait_event() with no timeout. A lost wake-up strands the shutdown worker on its single-threaded workqueue until some other sender releases the bit again - and on a connection that is being torn down precisely because it failed, there may never be another sender.

The barrier used to be there: release_in_xmit() did clear_bit() followed by smp_mb__after_atomic() until commit 1422f28826d2 ("rds: introduce acquire/release ordering in acquire/release_in_xmit()") folded both into clear_bit_unlock(), which strengthened the lock hand-off but silently dropped the full barrier the wake-up check depends on. The refill counterpart, release_refill() in net/rds/ib_recv.c, still carries its smp_mb__after_atomic() for exactly this reason.

Use wq_has_sleeper(), which is waitqueue_active() preceded by the required full barrier.

Text from CVE List

Affected versions 30

  • Linuxaffected: 1e1e4316fcaeb9cd6bc56c91127e88625237dd44 before 6f552364d97cf4005c7a58f11c9f79e14e269865CVE List
  • Linuxaffected: 8c378cc522aedd5fa5aa53486b43a4d552fbbd5c before a94b1dfc82454c5bc068e71c25393af674daf63bCVE List
  • Linuxaffected: 52287ed416a10bc3d3e204a3186d9509ab3ee634 before 5a806ed1eb46850ca4159a18b2a8c4b70f0c1341CVE List
  • Linuxaffected: 4a4dffdff9ea6201665f5d0a5042011d09bd527f before 3d401934b7edb3ccb07d982dabadd04c45ee307cCVE List
  • Linuxaffected: 1422f28826d2a0c11e5240b3e951c9e214d8656e before ed7ee0cd0e136d02f87f13181b1a89880463c7e9CVE List
  • Linuxaffected: 1422f28826d2a0c11e5240b3e951c9e214d8656e before a269795107f45adc95975a83324f8fef40bec4ceCVE List
  • Linuxaffected: 1422f28826d2a0c11e5240b3e951c9e214d8656e before 3764627b30a283e611e652c4a2bb8cdc74a75a99CVE List
  • Linuxaffected: 1422f28826d2a0c11e5240b3e951c9e214d8656e before 6d0c8b7073913011459cf968cbbadd341e166bc3CVE List
  • Linuxaffected: bec6c4ce1169a565c58c347d5d0ac22e46d507d6CVE List
  • Linuxaffected: f781fb5177cdfd9a6c98cd94e30275457c6461acCVE List
  • Linuxaffected: 917135195200e20e5244b9c3f2bb40f3d5e02510CVE List
  • Linuxaffected: d792459a6e2ae21c7f5107babd63e52e4c5ab93aCVE List
  • Linuxaffected: 5.10.214 before 5.10.271CVE List
  • Linuxaffected: 5.15.153 before 5.15.222CVE List
  • Linuxaffected: 6.1.83 before 6.1.189CVE List
  • Linuxaffected: 6.6.23 before 6.6.158CVE List
  • Linuxaffected: 4.19.311 before 4.20CVE List
  • Linuxaffected: 5.4.273 before 5.5CVE List
  • Linuxaffected: 6.7.11 before 6.8CVE List
  • Linuxaffected: 6.8.2 before 6.9CVE List
  • Linuxaffected: 6.9CVE List
  • Linuxunaffected: all versions before 6.9CVE List
  • Linuxunaffected: 5.10.271 through 5.10.*CVE List
  • Linuxunaffected: 5.15.222 through 5.15.*CVE List
  • Linuxunaffected: 6.1.189 through 6.1.*CVE List
  • Linuxunaffected: 6.6.158 through 6.6.*CVE List
  • Linuxunaffected: 6.12.111 through 6.12.*CVE List
  • Linuxunaffected: 6.18.53 through 6.18.*CVE List
  • Linuxunaffected: 7.2.7 through 7.2.*CVE List
  • Linuxunaffected: 7.3CVE List

References 8