Skip to content
Threat Brief

← All advisories

CVE-2026-98072

High 7.1No known exploitationFix available

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

Record last updated

CVSS score

7.1

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.1%

Higher than 2% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Patching and mitigation

Patch status
Fix available (source: NVD (reference tagged Patch))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
Microsoftazl3 kernel 6.6.157.1-1 on Azure Linux 3.0Not documented6.6.158.1-1Microsoft MSRC
Microsoftazl4 kernel 6.18.50-1.5.azl4 on Azure Linux 4.0Not documented0:6.18.57-1.1.azl4Microsoft MSRC
linuxlinux_kernelfrom 4.19.311 before 4.204.20NIST NVD
linuxlinux_kernelfrom 5.10.214 before 5.10.2715.10.271NIST NVD
linuxlinux_kernelfrom 5.15.153 before 5.15.2225.15.222NIST NVD
linuxlinux_kernelfrom 5.4.273 before 5.55.5NIST NVD
linuxlinux_kernelfrom 6.1.83 before 6.1.1896.1.189NIST NVD
linuxlinux_kernelfrom 6.13 before 6.18.536.18.53NIST NVD
linuxlinux_kernelfrom 6.19 before 7.2.77.2.7NIST NVD
linuxlinux_kernelfrom 6.6.23 before 6.6.1586.6.158NIST NVD
linuxlinux_kernelfrom 6.7.11 before 6.86.8NIST NVD
linuxlinux_kernelfrom 6.8.2 before 6.12.1116.12.111NIST NVD
linuxlinux_kernel7.3Not documentedNIST NVD

Timeline

  1. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  2. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (3.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Advisory change

    Microsoft advisory revised (4.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  5. Advisory change

    Microsoft advisory revised (5.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  6. Patch

    Fix documented by NVD (reference tagged Patch)

    Source: NVD (reference tagged Patch) (opens in a new tab)

Vendor guidance and references