Unknown

CVE-2026-98072 — net/rds: use wq_has_sleeper() in release_in_xmit()

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.

Published Sep 25, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+1

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.18%

ahead of 7% of scored CVEs · Oct 15, 2026

Affects

Linux

CVSS base

—

Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	version 917135195200e20e5244b9c3f2bb40f3d5e02510version 6.9≥ 6.8.2 and < 6.9≥ 6.7.11 and < 6.8≥ 5.4.273 and < 5.5≥ 4.19.311 and < 4.20≥ 6.6.23 and < 6.6.158≥ 6.1.83 and < 6.1.189 and 13 more ≥ 5.15.153 and < 5.15.222≥ 5.10.214 and < 5.10.271version d792459a6e2ae21c7f5107babd63e52e4c5ab93a≥ 1e1e4316fcaeb9cd6bc56c91127e88625237dd44 and < 6f552364d97cf4005c7a58f11c9f79e14e269865version f781fb5177cdfd9a6c98cd94e30275457c6461acversion bec6c4ce1169a565c58c347d5d0ac22e46d507d6≥ 1422f28826d2a0c11e5240b3e951c9e214d8656e and < 6d0c8b7073913011459cf968cbbadd341e166bc3≥ 1422f28826d2a0c11e5240b3e951c9e214d8656e and < 3764627b30a283e611e652c4a2bb8cdc74a75a99≥ 1422f28826d2a0c11e5240b3e951c9e214d8656e and < a269795107f45adc95975a83324f8fef40bec4ce≥ 1422f28826d2a0c11e5240b3e951c9e214d8656e and < ed7ee0cd0e136d02f87f13181b1a89880463c7e9≥ 4a4dffdff9ea6201665f5d0a5042011d09bd527f and < 3d401934b7edb3ccb07d982dabadd04c45ee307c≥ 52287ed416a10bc3d3e204a3186d9509ab3ee634 and < 5a806ed1eb46850ca4159a18b2a8c4b70f0c1341≥ 8c378cc522aedd5fa5aa53486b43a4d552fbbd5c and < a94b1dfc82454c5bc068e71c25393af674daf63b	Vulnerable	CVE Program (cve.org) e CISA ADP

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Not enough vector or weakness data: use the affected application’s logs as a starting point.

application logs

Timeline

What happened to this CVE, newest first.

2026
Record published
Oct 15, 2026
Affected products added · linux/linux
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Undergoing Analysis
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Sep 25, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

8 on the record

git.kernel.org/stable/c/3764627b30a283e611e652c4a2bb8cdc74a75a99
NIST National Vulnerability Database
git.kernel.org/stable/c/5a806ed1eb46850ca4159a18b2a8c4b70f0c1341
NIST National Vulnerability Database
git.kernel.org/stable/c/a94b1dfc82454c5bc068e71c25393af674daf63b
NIST National Vulnerability Database
git.kernel.org/stable/c/6f552364d97cf4005c7a58f11c9f79e14e269865
NIST National Vulnerability Database
git.kernel.org/stable/c/ed7ee0cd0e136d02f87f13181b1a89880463c7e9
NIST National Vulnerability Database
git.kernel.org/stable/c/a269795107f45adc95975a83324f8fef40bec4ce
NIST National Vulnerability Database
git.kernel.org/stable/c/3d401934b7edb3ccb07d982dabadd04c45ee307c
NIST National Vulnerability Database
git.kernel.org/stable/c/6d0c8b7073913011459cf968cbbadd341e166bc3
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 1d
Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 1d
Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No CVSS score published by NVD, the CNA, CISA or GitHub so far.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-98072 is "net/rds: use wq_has_sleeper() in release_in_xmit()", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.