CVE-2026-92510

Vulnérabilité élevée dans Linux (Linux)

CVSS 7.8 · Élevée
EPSS 0.1%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, <5.13, 0, 6.1.188, 6.18.52, <=6.6.*, 48f8a70e899fa4d9c8f00369f482f0382173ece9, 6.6.157, <95c992c869df54a6a7061f5f3fb6400244f2af8f, 7.2.6, 5.13, <=6.18.*, <a5bfd9fe05d5cebbd3e447bf7f7b2c663007d8b9, 6.12.110, <=7.2.*, <d3d0eabe6e39b024deb3e085e2d408d037e967c3, <9c704383529044c02122f85a2a9a42cbf14a07a6, <=*, <88244ecc71cc0b3ed200f5ef7ddea6686adfd730, <bedd7dee72588c838f5b67197ea8b387e7beb918, 7.3

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix potential use after free in ib_destroy_srq_user() When accessing a SRQ via the netlink path the only synchronization mechanism for the said SRQ is rdma_restrack_get(). Currently, rdma_restrack_del() is invoked at the end of ib_destroy_srq_user(), which is too late, since by that point vendor-specific resources associated with the SRQ might already be freed. This can leave a short window where the SRQ remains accessible through restrack, leading to a potential use-after-free. Fix this by moving the rdma_restrack_begin_del() call to the start of ib_destroy_srq_user(), ensuring that the SRQ is removed from restrack before its internal resources are released. This guarantees that no new users hold references to a SRQ that is in the process of destruction. In addition, this change preserves the intended inverted order between create and destroy routines: resources are added to restrack at the end of successful creation, and hence shall be removed from the restrack first thing during the destruction flow, which keeps the lifecycle management consistent and predictable.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, <5.13, 0, 6.1.188, 6.18.52, <=6.6.*, 48f8a70e899fa4d9c8f00369f482f0382173ece9, 6.6.157, <95c992c869df54a6a7061f5f3fb6400244f2af8f, 7.2.6, 5.13, <=6.18.*, <a5bfd9fe05d5cebbd3e447bf7f7b2c663007d8b9, 6.12.110, <=7.2.*, <d3d0eabe6e39b024deb3e085e2d408d037e967c3, <9c704383529044c02122f85a2a9a42cbf14a07a6, <=*, <88244ecc71cc0b3ed200f5ef7ddea6686adfd730, <bedd7dee72588c838f5b67197ea8b387e7beb918, 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