CVE-2026-90081

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, 5.15.221, 5.10.270, 0, 6.1.188, <2a809d7896dbf18e1ecfbdd930f71c9fc298b16d, 6.18.52, <=5.10.*, 2.6.30, <=6.6.*, 6.6.157, <bf2b8130723efcb5b86c3ddb6317c3a9b2a9cfc5, 7.2.6, 922cb17a5c812fcc9ebee249f4109db099896941, <2.6.30, <=6.18.*, 6.12.110, <281f9fda2e06d6c211bb365a5379ed2e05cc2e21, <=7.2.*, <0e169f6a2adeb17b5577ed7e8abd642465bb50ec, <fa4b98e891fda28cc0638d809c6125ec63d8319d, <d4f484661961636eb90d287050959e613795f73a, <42884bd8b8fd023d6a610a695bd5ddd1d5dece17, <=*, <=5.15.*, <a526214b9f0548ca0e53a6e0d1727d8ea9befc23, 7.3

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.

Gravité et risque d'exploitation

CVE-2026-90081 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.21 %, ce qui la place devant 10.7 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 5.15.221, 5.10.270, 0, 6.1.188, <2a809d7896dbf18e1ecfbdd930f71c9fc298b16d, 6.18.52, <=5.10.*, 2.6.30, <=6.6.*, 6.6.157, <bf2b8130723efcb5b86c3ddb6317c3a9b2a9cfc5, 7.2.6, 922cb17a5c812fcc9ebee249f4109db099896941, <2.6.30, <=6.18.*, 6.12.110, <281f9fda2e06d6c211bb365a5379ed2e05cc2e21, <=7.2.*, <0e169f6a2adeb17b5577ed7e8abd642465bb50ec, <fa4b98e891fda28cc0638d809c6125ec63d8319d, <d4f484661961636eb90d287050959e613795f73a, <42884bd8b8fd023d6a610a695bd5ddd1d5dece17, <=*, <=5.15.*, <a526214b9f0548ca0e53a6e0d1727d8ea9befc23, 7.3) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références