---
id: CVE-2026-98072
title: |-
  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 an…
summary: |-
  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 an…
severity: medium
cvss: 5.5
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'
cwe:
  - CWE-821
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 1e1e4316fcaeb9cd6bc56c91127e88625237dd44 <
    6f552364d97cf4005c7a58f11c9f79e14e269865
  - >-
    Linux >= 8c378cc522aedd5fa5aa53486b43a4d552fbbd5c <
    a94b1dfc82454c5bc068e71c25393af674daf63b
  - >-
    Linux >= 52287ed416a10bc3d3e204a3186d9509ab3ee634 <
    5a806ed1eb46850ca4159a18b2a8c4b70f0c1341
  - >-
    Linux >= 4a4dffdff9ea6201665f5d0a5042011d09bd527f <
    3d401934b7edb3ccb07d982dabadd04c45ee307c
  - >-
    Linux >= 1422f28826d2a0c11e5240b3e951c9e214d8656e <
    ed7ee0cd0e136d02f87f13181b1a89880463c7e9
  - >-
    Linux >= 1422f28826d2a0c11e5240b3e951c9e214d8656e <
    a269795107f45adc95975a83324f8fef40bec4ce
  - >-
    Linux >= 1422f28826d2a0c11e5240b3e951c9e214d8656e <
    3764627b30a283e611e652c4a2bb8cdc74a75a99
  - >-
    Linux >= 1422f28826d2a0c11e5240b3e951c9e214d8656e <
    6d0c8b7073913011459cf968cbbadd341e166bc3
  - Linux bec6c4ce1169a565c58c347d5d0ac22e46d507d6
  - Linux f781fb5177cdfd9a6c98cd94e30275457c6461ac
  - Linux 917135195200e20e5244b9c3f2bb40f3d5e02510
  - Linux d792459a6e2ae21c7f5107babd63e52e4c5ab93a
  - Linux >= 5.10.214 < 5.10.271
  - Linux >= 5.15.153 < 5.15.222
  - Linux >= 6.1.83 < 6.1.189
  - Linux >= 6.6.23 < 6.6.158
  - Linux >= 4.19.311 < 4.20
  - Linux >= 5.4.273 < 5.5
  - Linux >= 6.7.11 < 6.8
  - Linux >= 6.8.2 < 6.9
  - Linux 6.9
published: '2026-09-25'
updated: '2026-10-03'
sourceUpdated: '2026-10-03T11:18:28.503'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-98072'
references:
  - url: 'https://git.kernel.org/stable/c/3764627b30a283e611e652c4a2bb8cdc74a75a99'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/3d401934b7edb3ccb07d982dabadd04c45ee307c'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/5a806ed1eb46850ca4159a18b2a8c4b70f0c1341'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/6d0c8b7073913011459cf968cbbadd341e166bc3'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/6f552364d97cf4005c7a58f11c9f79e14e269865'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/a269795107f45adc95975a83324f8fef40bec4ce'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/a94b1dfc82454c5bc068e71c25393af674daf63b'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/ed7ee0cd0e136d02f87f13181b1a89880463c7e9'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: >-
      https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98072.json
  - url: 'https://access.redhat.com/security/cve/CVE-2026-98072'
  - url: 'https://bugzilla.redhat.com/show_bug.cgi?id=2541116'
  - url: 'https://www.cve.org/CVERecord?id=CVE-2026-98072'
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2026-98072'
  - url: >-
      https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2026/CVE-2026-98072.mbox
tags:
  - nvd
  - cve.org
  - csaf
  - vex
  - red-hat
epss: 0.00176
epssPercentile: 0.07122
cvssSource: vendor
ingestedAt: '2026-09-25T11:06:38.838Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.

## Vendor advisories

- **Red Hat VEX** · Moderate · affected: Red Hat Enterprise Linux 6 · no fix planned: Red Hat Enterprise Linux 6 · updated 2026-10-17 · [vex](https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98072.json)