Heimdall Security Logo

CVE-2026-53186

Vulnérabilité critique dans Linux (Linux)

CVSS 9.1 · Critique
EPSS 0.5%
Linux•Linux•Versions : <=6.1.*, <=7.0.*, <=6.12.*, 6.12.94, <ed77cc819ad631264787cade5ae5ec4c535ec6bb, <f92a285db7ff6e598591ccbfb551be155c5f4d57, <0d64bc200ebe4f275b27438c6e593903e0b16fe1, 0, aef9ec39c47f0cece886ddd6b53c440321e0b2a6, 6.1.176, 5.15.210, <=5.10.*, <=6.6.*, <0b9ee09d5e849591f17d98c078033dadea967293, 7.0.13, 6.18.36, <2015038195939eac54a1ee83c9d98ef1a8ccbbce, 7.1, <2.6.15, <=6.18.*, <3889517c2ec7f364914aea8209abfff735f7ecde, <13e91fd076306f5d0cdfa14f53d69e37274723c4, 2.6.15, <=*, <=5.15.*, <3523e53ff95f1837ec3f57ff7558532bcb2661b7, 6.6.143, 5.10.259

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/srp: bound SRP_RSP sense copy by the received length srp_process_rsp() copies sense data from rsp->data + resp_data_len, where resp_data_len is the full 32-bit value supplied by the SRP target and is never checked against the number of bytes actually received (wc->byte_len). The copy length is bounded to SCSI_SENSE_BUFFERSIZE, so at most 96 bytes are copied, but the source offset is not bounded. A malicious or compromised SRP target on the InfiniBand/RoCE fabric that the initiator has logged into can return an SRP_RSP with SRP_RSP_FLAG_SNSVALID set and a large resp_data_len. The receive buffer is allocated at the target-chosen max_ti_iu_len, so the source of the sense copy lands past the bytes actually received; with resp_data_len near 0xFFFFFFFF it is gigabytes past the buffer and the read faults. Copy the sense data only if it has not been truncated, that is, only if the response header, the response data, and the sense region fit within the bytes actually received; otherwise drop the sense and log. The in-tree iSER and NVMe-RDMA receive paths already bound their parse by wc->byte_len; this brings ib_srp into line with them.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=7.0.*, <=6.12.*, 6.12.94, <ed77cc819ad631264787cade5ae5ec4c535ec6bb, <f92a285db7ff6e598591ccbfb551be155c5f4d57, <0d64bc200ebe4f275b27438c6e593903e0b16fe1, 0, aef9ec39c47f0cece886ddd6b53c440321e0b2a6, 6.1.176, 5.15.210, <=5.10.*, <=6.6.*, <0b9ee09d5e849591f17d98c078033dadea967293, 7.0.13, 6.18.36, <2015038195939eac54a1ee83c9d98ef1a8ccbbce, 7.1, <2.6.15, <=6.18.*, <3889517c2ec7f364914aea8209abfff735f7ecde, <13e91fd076306f5d0cdfa14f53d69e37274723c4, 2.6.15, <=*, <=5.15.*, <3523e53ff95f1837ec3f57ff7558532bcb2661b7, 6.6.143, 5.10.259) 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

Rechercher une autre CVE