net/rds: use wq_has_sleeper() in release_in_xmit()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 5.10.271, Kernel 5.15.222, Kernel 5.5 and 16 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =7.3, >=5.10.214 <5.10.271, >=5.15.153 <5.15.222, >=5.4.273 <5.5, >=6.1.83 <6.1.189, >=6.13 <6.18.53, >=6.19 <7.2.7, >=6.6.23 <6.6.158, >=6.7.11 <6.8, >=6.8.2 <6.12.111, >=4.19.311 <4.20, >=4a4dffdff9ea6201665f5d0a5042011d09bd527f <3d401934b7edb3ccb07d982dabadd04c45ee307c, >=52287ed416a10bc3d3e204a3186d9509ab3ee634 <5a806ed1eb46850ca4159a18b2a8c4b70f0c1341, >=6.8.2 <6.9, >=8c378cc522aedd5fa5aa53486b43a4d552fbbd5c <a94b1dfc82454c5bc068e71c25393af674daf63b, =6.9, =917135195200e20e5244b9c3f2bb40f3d5e02510, =bec6c4ce1169a565c58c347d5d0ac22e46d507d6, =d792459a6e2ae21c7f5107babd63e52e4c5ab93a, =f781fb5177cdfd9a6c98cd94e30275457c6461ac, >=1422f28826d2a0c11e5240b3e951c9e214d8656e <3764627b30a283e611e652c4a2bb8cdc74a75a99, >=1422f28826d2a0c11e5240b3e951c9e214d8656e <6d0c8b7073913011459cf968cbbadd341e166bc3, >=1422f28826d2a0c11e5240b3e951c9e214d8656e <a269795107f45adc95975a83324f8fef40bec4ce, >=1422f28826d2a0c11e5240b3e951c9e214d8656e <ed7ee0cd0e136d02f87f13181b1a89880463c7e9, >=1e1e4316fcaeb9cd6bc56c91127e88625237dd44 <6f552364d97cf4005c7a58f11c9f79e14e269865 | 5.10.271, 5.15.222, 5.5, 6.1.189, 6.18.53, 7.2.7, 6.6.158, 6.8, 6.12.111, 4.20, 3d401934b7edb3ccb07d982dabadd04c45ee307c, 5a806ed1eb46850ca4159a18b2a8c4b70f0c1341, 6.9, a94b1dfc82454c5bc068e71c25393af674daf63b, 3764627b30a283e611e652c4a2bb8cdc74a75a99, 6d0c8b7073913011459cf968cbbadd341e166bc3, a269795107f45adc95975a83324f8fef40bec4ce, ed7ee0cd0e136d02f87f13181b1a89880463c7e9, 6f552364d97cf4005c7a58f11c9f79e14e269865 |
| linux-kernel: Kernel | >=4.19.311 <4.20, >=5.10.214 <5.10.271, >=5.15.153 <5.15.222, >=5.4.273 <5.5, >=6.1.83 <6.1.189, >=6.13.0 <6.18.53, >=6.19.0 <7.2.7, >=6.6.23 <6.6.158, >=6.7.11 <6.8, >=6.8.2 <6.9, >=6.9.0 <6.12.111 | 4.20, 5.10.271, 5.15.222, 5.5, 6.1.189, 6.18.53, 7.2.7, 6.6.158, 6.8, 6.9, 6.12.111 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket