Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-90081net/rds: use wq_has_sleeper() in rds_cong_map_updated()

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 922cb17a5c812fcc9ebee249f4109db099896941 – < 2a809d7896dbf18e1ecfbdd930f71c9fc298b16d
    • affected 922cb17a5c812fcc9ebee249f4109db099896941 – < fa4b98e891fda28cc0638d809c6125ec63d8319d
    • affected 922cb17a5c812fcc9ebee249f4109db099896941 – < 0e169f6a2adeb17b5577ed7e8abd642465bb50ec
    • affected 922cb17a5c812fcc9ebee249f4109db099896941 – < 42884bd8b8fd023d6a610a695bd5ddd1d5dece17
    • affected 922cb17a5c812fcc9ebee249f4109db099896941 – < a526214b9f0548ca0e53a6e0d1727d8ea9befc23
    • affected 922cb17a5c812fcc9ebee249f4109db099896941 – < bf2b8130723efcb5b86c3ddb6317c3a9b2a9cfc5
    • affected 922cb17a5c812fcc9ebee249f4109db099896941 – < 281f9fda2e06d6c211bb365a5379ed2e05cc2e21
    • affected 922cb17a5c812fcc9ebee249f4109db099896941 – < d4f484661961636eb90d287050959e613795f73a
  • Linux · Linux

    • affected 2.6.30
    • unaffected < 2.6.30
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90081 badge
[![CVE-2026-90081](https://cveledger.app/badge/CVE-2026-90081.svg)](https://cveledger.app/cve/CVE-2026-90081)

Record last updated .