CVE-2026-90081
Description
In the Linux kernel, the following vulnerability has been resolved: net/rds: use wq_has_sleeper() in rds_cong_map_updated() rds_cong_map_updated() runs after a peer's congestion map has been rewritten (by rds_tcp_cong_recv() and rds_ib_cong_recv(), or the clear-all in the loopback and IB send-completion paths). It bumps rds_cong_generation and then checks waitqueue_active() on map->m_waitq and on rds_poll_waitq to decide whether anyone needs waking. atomic_inc() carries no ordering and waitqueue_active() is a plain load, so nothing orders the map and generation stores before the wait queue reads. The waiters do the mirror image: rds_cong_wait() adds itself to m_waitq and then tests the port bit, and rds_poll() registers on rds_poll_waitq and then reads the generation. That is the store-buffering pattern described above waitqueue_active() in include/linux/wait.h - the updater can observe an empty wait queue while the waiter still observes the port as congested, and no wake-up is issued. rds_cong_wait() is an interruptible sleep with no timeout, so a sender blocked on a congested port stays blocked until the next congestion update from that peer arrives or a signal is delivered. A poll() waiter misses the map-updated notification the same way. Use wq_has_sleeper(), which is waitqueue_active() preceded by the required full barrier, as rds_tcp_state_change() already does for the same pattern.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
Propose a mitigation on Community Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
References
- https://git.kernel.org/stable/c/0e169f6a2adeb17b5577ed7e8abd642465bb50ec
- https://git.kernel.org/stable/c/281f9fda2e06d6c211bb365a5379ed2e05cc2e21
- https://git.kernel.org/stable/c/2a809d7896dbf18e1ecfbdd930f71c9fc298b16d
- https://git.kernel.org/stable/c/42884bd8b8fd023d6a610a695bd5ddd1d5dece17
- https://git.kernel.org/stable/c/a526214b9f0548ca0e53a6e0d1727d8ea9befc23
- https://git.kernel.org/stable/c/bf2b8130723efcb5b86c3ddb6317c3a9b2a9cfc5
- https://git.kernel.org/stable/c/d4f484661961636eb90d287050959e613795f73a
- https://git.kernel.org/stable/c/fa4b98e891fda28cc0638d809c6125ec63d8319d
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.