CVE-2026-98072

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.

Gravité et risque d'exploitation

CVE-2026-98072 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.18 %, ce qui la place devant 6.7 % des CVE référencées.

Que faire ?

• Vérifiez si Linux (versions 6.9, <3d401934b7edb3ccb07d982dabadd04c45ee307c, d792459a6e2ae21c7f5107babd63e52e4c5ab93a, <=6.1.*, <=6.12.*, 7.2.7, 1422f28826d2a0c11e5240b3e951c9e214d8656e, f781fb5177cdfd9a6c98cd94e30275457c6461ac, 6.18.53, 0, 917135195200e20e5244b9c3f2bb40f3d5e02510, 6.1.83, 4.19.311, 6.7.11, 5.15.153, <6f552364d97cf4005c7a58f11c9f79e14e269865, <5.10.271, <a269795107f45adc95975a83324f8fef40bec4ce, <6.8, <4.20, 5.10.271, 6.6.158, 6.8.2, <=5.10.*, <=6.6.*, 6.1.189, 5.4.273, <6.6.158, <5.15.222, <6d0c8b7073913011459cf968cbbadd341e166bc3, <5a806ed1eb46850ca4159a18b2a8c4b70f0c1341, <5.5, <=6.18.*, 5.15.222, <ed7ee0cd0e136d02f87f13181b1a89880463c7e9, <3764627b30a283e611e652c4a2bb8cdc74a75a99, 8c378cc522aedd5fa5aa53486b43a4d552fbbd5c, <=7.2.*, <6.1.189, 6.6.23, bec6c4ce1169a565c58c347d5d0ac22e46d507d6, 52287ed416a10bc3d3e204a3186d9509ab3ee634, 5.10.214, 1e1e4316fcaeb9cd6bc56c91127e88625237dd44, <=*, <=5.15.*, 4a4dffdff9ea6201665f5d0a5042011d09bd527f, <6.9, <a94b1dfc82454c5bc068e71c25393af674daf63b, 6.12.111, 7.3) est présent sur votre parc.
• Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
• À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
• Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

• https://git.kernel.org/stable/c/6f552364d97cf4005c7a58f11c9f79e14e269865
• https://git.kernel.org/stable/c/a94b1dfc82454c5bc068e71c25393af674daf63b
• https://git.kernel.org/stable/c/5a806ed1eb46850ca4159a18b2a8c4b70f0c1341
• https://git.kernel.org/stable/c/3d401934b7edb3ccb07d982dabadd04c45ee307c
• https://git.kernel.org/stable/c/ed7ee0cd0e136d02f87f13181b1a89880463c7e9
• https://git.kernel.org/stable/c/a269795107f45adc95975a83324f8fef40bec4ce
• https://git.kernel.org/stable/c/3764627b30a283e611e652c4a2bb8cdc74a75a99
• https://git.kernel.org/stable/c/6d0c8b7073913011459cf968cbbadd341e166bc3