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

MITRE NVD CVE.ORG JSON API

Summary

CVECVE-2026-98072
StatePUBLISHED
AssignerLinux
Source PriorityCVE Program / NVD first with legacy fallback
Published2026-09-25 11:17:36 UTC
Updated2026-09-25 11:17:36 UTC
DescriptionIn 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.

Vendor Declared Affected Products

SourceVendorProductVersionPlatforms
CNA Linux Linux affected 1422f28826d2a0c11e5240b3e951c9e214d8656e ed7ee0cd0e136d02f87f13181b1a89880463c7e9 git Not specified
CNA Linux Linux affected 1422f28826d2a0c11e5240b3e951c9e214d8656e a269795107f45adc95975a83324f8fef40bec4ce git Not specified
CNA Linux Linux affected 1422f28826d2a0c11e5240b3e951c9e214d8656e 3764627b30a283e611e652c4a2bb8cdc74a75a99 git Not specified
CNA Linux Linux affected 1422f28826d2a0c11e5240b3e951c9e214d8656e 6d0c8b7073913011459cf968cbbadd341e166bc3 git Not specified
CNA Linux Linux affected bec6c4ce1169a565c58c347d5d0ac22e46d507d6 git Not specified
CNA Linux Linux affected f781fb5177cdfd9a6c98cd94e30275457c6461ac git Not specified
CNA Linux Linux affected 1e1e4316fcaeb9cd6bc56c91127e88625237dd44 git Not specified
CNA Linux Linux affected 8c378cc522aedd5fa5aa53486b43a4d552fbbd5c git Not specified
CNA Linux Linux affected 52287ed416a10bc3d3e204a3186d9509ab3ee634 git Not specified
CNA Linux Linux affected 4a4dffdff9ea6201665f5d0a5042011d09bd527f git Not specified
CNA Linux Linux affected 917135195200e20e5244b9c3f2bb40f3d5e02510 git Not specified
CNA Linux Linux affected d792459a6e2ae21c7f5107babd63e52e4c5ab93a git Not specified
CNA Linux Linux affected 4.19.311 4.20 semver Not specified
CNA Linux Linux affected 5.4.273 5.5 semver Not specified
CNA Linux Linux affected 5.10.214 5.11 semver Not specified
CNA Linux Linux affected 5.15.153 5.16 semver Not specified
CNA Linux Linux affected 6.1.83 6.2 semver Not specified
CNA Linux Linux affected 6.6.23 6.7 semver Not specified
CNA Linux Linux affected 6.7.11 6.8 semver Not specified
CNA Linux Linux affected 6.8.2 6.9 semver Not specified
CNA Linux Linux affected 6.9 Not specified
CNA Linux Linux unaffected 6.9 semver Not specified
CNA Linux Linux unaffected 6.12.111 6.12.* semver Not specified
CNA Linux Linux unaffected 6.18.53 6.18.* semver Not specified
CNA Linux Linux unaffected 7.2.7 7.2.* semver Not specified
CNA Linux Linux unaffected 7.3-rc2 * original_commit_for_fix Not specified

References

ReferenceSourceLinkTags
git.kernel.org/stable/c/3764627b30a283e611e652c4a2bb8cdc74a75a99 416baaa9-dc9f-4396-8d5f-8c081fb06d67 git.kernel.org
git.kernel.org/stable/c/6d0c8b7073913011459cf968cbbadd341e166bc3 416baaa9-dc9f-4396-8d5f-8c081fb06d67 git.kernel.org
git.kernel.org/stable/c/a269795107f45adc95975a83324f8fef40bec4ce 416baaa9-dc9f-4396-8d5f-8c081fb06d67 git.kernel.org
git.kernel.org/stable/c/ed7ee0cd0e136d02f87f13181b1a89880463c7e9 416baaa9-dc9f-4396-8d5f-8c081fb06d67 git.kernel.org
CVE Program record CVE.ORG www.cve.org canonical
NVD vulnerability detail NVD nvd.nist.gov canonical, analysis

© CVE.report 2026

Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. It is the responsibility of user to evaluate the accuracy, completeness or usefulness of any information, opinion, advice or other content. EACH USER WILL BE SOLELY RESPONSIBLE FOR ANY consequences of his or her direct or indirect use of this web site. ALL WARRANTIES OF ANY KIND ARE EXPRESSLY DISCLAIMED. This site will NOT BE LIABLE FOR ANY DIRECT, INDIRECT or any other kind of loss.

CVE, CWE, and OVAL are registred trademarks of The MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. This site includes MITRE data granted under the following license.

Free CVE JSON API cve.report/api

CVE.report and Source URL Uptime Status status.cve.report