Answer in brief
CVE-2026-90081 records a Unknown severity vulnerability in net/rds: use wq_has_sleeper() in rds_cong_map_updated(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=922cb17a5c812fcc9ebee249f4109db099896941 <2a809d7896dbf18e1ecfbdd930f71c9fc298b16d || >=922cb17a5c812fcc9ebee249f4109db099896941 <fa4b98e891fda28cc0638d809c6125ec63d8319d || >=922cb17a5c812fcc9ebee249f4109db099896941 <0e169f6a2adeb17b5577ed7e8abd642465bb50ec || >=922cb17a5c812fcc9ebee249f4109db099896941 <42884bd8b8fd023d6a610a695bd5ddd1d5dece17 || >=922cb17a5c812fcc9ebee249f4109db099896941 <a526214b9f0548ca0e53a6e0d1727d8ea9befc23 || >=922cb17a5c812fcc9ebee249f4109db099896941 <bf2b8130723efcb5b86c3ddb6317c3a9b2a9cfc5 || >=922cb17a5c812fcc9ebee249f4109db099896941 <281f9fda2e06d6c211bb365a5379ed2e05cc2e21 || >=922cb17a5c812fcc9ebee249f4109db099896941 <d4f484661961636eb90d287050959e613795f73a | 2a809d7896dbf18e1ecfbdd930f71c9fc298b16d, fa4b98e891fda28cc0638d809c6125ec63d8319d, 0e169f6a2adeb17b5577ed7e8abd642465bb50ec, 42884bd8b8fd023d6a610a695bd5ddd1d5dece17, a526214b9f0548ca0e53a6e0d1727d8ea9befc23, bf2b8130723efcb5b86c3ddb6317c3a9b2a9cfc5, 281f9fda2e06d6c211bb365a5379ed2e05cc2e21, d4f484661961636eb90d287050959e613795f73a |
| Linux/Linuxgeneric | 2.6.30 | Not reported |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.