{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90081 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90081 is a vulnerability in Linux, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-90081 and fix it if it is affected.\n\nWhat it is: CVE-2026-90081 is a vulnerability in Linux, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-90081 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-90081/ (Markdown: https://insights.sbomify.com/CVE-2026-90081/index.md)","id":"CVE-2026-90081","markdown":"https://insights.sbomify.com/CVE-2026-90081/index.md","name":"CVE-2026-90081","record":{"aliases":["AZL-102839","BELL-CVE-2026-90081","DEBIAN-CVE-2026-90081","GHSA-23r9-76mg-5gpp","UBUNTU-CVE-2026-90081"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel RDS","requires_auth":"none","summary":"A race condition in the Linux kernel RDS module can cause senders to block indefinitely, leading to a denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet/rds: use wq_has_sleeper() in rds_cong_map_updated()\n\nrds_cong_map_updated() runs after a peer's congestion map has been\nrewritten (by rds_tcp_cong_recv() and rds_ib_cong_recv(), or the\nclear-all in the loopback and IB send-completion paths).  It bumps\nrds_cong_generation and then checks waitqueue_active() on\nmap-\u003em_waitq and on rds_poll_waitq to decide whether anyone needs\nwaking.  atomic_inc() carries no ordering and waitqueue_active() is a\nplain load, so nothing orders the map and generation stores before\nthe wait queue reads.  The waiters do the mirror image: rds_cong_wait()\nadds itself to m_waitq and then tests the port bit, and rds_poll()\nregisters on rds_poll_waitq and then reads the generation.  That is\nthe store-buffering pattern described above waitqueue_active() in\ninclude/linux/wait.h - the updater can observe an empty wait queue\nwhile the waiter still observes the port as congested, and no wake-up\nis issued.\n\nrds_cong_wait() is an interruptible sleep with no timeout, so a\nsender blocked on a congested port stays blocked until the next\ncongestion update from that peer arrives or a signal is delivered.\nA poll() waiter misses the map-updated notification the same way.\n\nUse wq_has_sleeper(), which is waitqueue_active() preceded by the\nrequired full barrier, as rds_tcp_state_change() already does for\nthe same pattern.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"net/rds: use wq_has_sleeper() in rds_cong_map_updated()","id":"CVE-2026-90081","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"net: mana: Cap MSI-X vectors to the device MSI-X table size","id":"CVE-2026-90082"},"packages":[],"prev":{"headline":"octeontx2-pf: fix NULL deref of af_xdp_zc_qidx on rep setup","id":"CVE-2026-90080"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A race condition in the Linux kernel RDS module can cause senders to block indefinitely, leading to a denial of service.","url":"https://insights.sbomify.com/CVE-2026-90081/"}