CVE-2026-98072: net/rds: use wq_has_sleeper() in release_in_xmit()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 3764627b30a283e611e652c4a2bb8cdc74a75a99, 3d401934b7edb3ccb07d982dabadd04c45ee307c, 4.20; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 3764627b30a283e611e652c4a2bb8cdc74a75a99, 3d401934b7edb3ccb07d982dabadd04c45ee307c, 4.20; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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 19, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- bec6c4ce1169a565c58c347d5d0ac22e46d507d6, f781fb5177cdfd9a6c98cd94e30275457c6461ac, 917135195200e20e5244b9c3f2bb40f3d5e02510, d792459a6e2ae21c7f5107babd63e52e4c5ab93a, 6.9affected
- 1e1e4316fcaeb9cd6bc56c91127e88625237dd44 and later · before 6f552364d97cf4005c7a58f11c9f79e14e269865affected · git
- 8c378cc522aedd5fa5aa53486b43a4d552fbbd5c and later · before a94b1dfc82454c5bc068e71c25393af674daf63baffected · git
- 52287ed416a10bc3d3e204a3186d9509ab3ee634 and later · before 5a806ed1eb46850ca4159a18b2a8c4b70f0c1341affected · git
- 4a4dffdff9ea6201665f5d0a5042011d09bd527f and later · before 3d401934b7edb3ccb07d982dabadd04c45ee307caffected · git
- 1422f28826d2a0c11e5240b3e951c9e214d8656e and later · before ed7ee0cd0e136d02f87f13181b1a89880463c7e9affected · git
- 1422f28826d2a0c11e5240b3e951c9e214d8656e and later · before a269795107f45adc95975a83324f8fef40bec4ceaffected · git
- 1422f28826d2a0c11e5240b3e951c9e214d8656e and later · before 3764627b30a283e611e652c4a2bb8cdc74a75a99affected · git
- 1422f28826d2a0c11e5240b3e951c9e214d8656e and later · before 6d0c8b7073913011459cf968cbbadd341e166bc3affected · git
- 5.10.214 and later · before 5.10.271affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.7-1 | 7.2.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98070Sep 25, 2026 · net/rds: acquire RDS_IN_XMIT in rds_tcp_reset_callbacks()32Monitor
- ← EarlierCVE-2026-98071Sep 25, 2026 · net/rds: clear cp_flags bits individually in rds_conn_path_reset()0Monitor
- Later →CVE-2026-98073Sep 25, 2026 · net: Remove conflicting altnames for dying netns in __dev_change_net_namespace().31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3764627b30a283e611e652c4a2bb8cdc74a75a99 | Vendor (CNA) |
| Linux Linux | 3d401934b7edb3ccb07d982dabadd04c45ee307c | Vendor (CNA) |
| Linux Linux | 4.20 | Vendor (CNA) |
| Linux Linux | 5.10.271 | Vendor (CNA) |
| Linux Linux | 5.15.222 | Vendor (CNA) |
| Linux Linux | 5.5 | Vendor (CNA) |
| Linux Linux | 5a806ed1eb46850ca4159a18b2a8c4b70f0c1341 | Vendor (CNA) |
| Linux Linux | 6.1.189 | Vendor (CNA) |
| Linux Linux | 6.6.158 | Vendor (CNA) |
| Linux Linux | 6.8 | Vendor (CNA) |
| Linux Linux | 6.9 | Vendor (CNA) |
| Linux Linux | 6d0c8b7073913011459cf968cbbadd341e166bc3 | Vendor (CNA) |
| Linux Linux | 6f552364d97cf4005c7a58f11c9f79e14e269865 | Vendor (CNA) |
| Linux Linux | a269795107f45adc95975a83324f8fef40bec4ce | Vendor (CNA) |
| Linux Linux | a94b1dfc82454c5bc068e71c25393af674daf63b | Vendor (CNA) |
| Linux Linux | ed7ee0cd0e136d02f87f13181b1a89880463c7e9 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1184 · Sep 28, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/3d401934b7edb3ccb07d982dabadd04c45ee307c
- git.kernel.org/stable/c/5a806ed1eb46850ca4159a18b2a8c4b70f0c1341
- git.kernel.org/stable/c/6d0c8b7073913011459cf968cbbadd341e166bc3
- git.kernel.org/stable/c/6f552364d97cf4005c7a58f11c9f79e14e269865
- git.kernel.org/stable/c/a269795107f45adc95975a83324f8fef40bec4ce
- git.kernel.org/stable/c/a94b1dfc82454c5bc068e71c25393af674daf63b
- git.kernel.org/stable/c/ed7ee0cd0e136d02f87f13181b1a89880463c7e9
Vendor advisories and official records. Exploit/PoC links are deliberately left out.