Heimdall Security Logo

CVE-2026-89480

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

CVSS 7.5 · Élevée
EPSS 0.4%
Linux•Linux•Versions : <=6.1.*, <7fa3f73f6c8ddc5f0425b50fb2a626a782ef7d12, <=6.12.*, 5.15.221, <a5c1bb0fb1bab2f24a081339c145870697f6d220, 0, 7.2.4, 6.1.188, <fca3ebb63e5c82561cd9934365dcc0d068008006, <8a02ad98798fd01f51f648c1fdd8f3c9d07195d3, <=6.6.*, 5.0, 6.6.157, <5.0, <=6.18.*, 3f2304f8c6d6ed97849057bd16fee99e434ca796, <=7.2.*, <=*, <832a685efeb5d925ee7d30011d2dbe45f81447a3, <=5.15.*, <99066cf9bba175f610ceb61a35f6fc9fbc33ff65, 6.18.50, 6.12.109, <aa107e3a68f4af177d60f2d87679e7f67179a36c, 7.3

Description

In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: reject a read that transferred too few bytes nvme_tcp_recv_data() completes a request once the current C2HData PDU has been consumed. Nothing compares the total bytes received against the length the command asked for: struct nvme_tcp_request has no receive-side counter, queue->data_remaining is per queue, and blk_mq_end_request() completes for blk_rq_bytes(rq) unconditionally with no residual concept anywhere above. A controller can therefore answer a 4096-byte read with 512 bytes and have it reported as a complete read; user space then gets 4096 bytes of which 3584 are whatever was already in the page. I reproduced that with a test target. Count the bytes received and refuse to complete a successful read whose count does not match, at the two NVME_TCP_F_DATA_SUCCESS paths and in nvme_tcp_process_nvme_cqe(). The success test shifts req->status right by one, because the driver keeps the wire value there and shifts it on completion, so the check must see what the completion path will see. Only REQ_OP_READ is checked, because there the length comes from the sectors the request covers; a passthrough command is built by its submitter, which picks both command and buffer, so the kernel has nothing to compare against.

Gravité et risque d'exploitation

CVE-2026-89480 obtient un score CVSS de 7.5/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.41 %, ce qui la place devant 34.4 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <7fa3f73f6c8ddc5f0425b50fb2a626a782ef7d12, <=6.12.*, 5.15.221, <a5c1bb0fb1bab2f24a081339c145870697f6d220, 0, 7.2.4, 6.1.188, <fca3ebb63e5c82561cd9934365dcc0d068008006, <8a02ad98798fd01f51f648c1fdd8f3c9d07195d3, <=6.6.*, 5.0, 6.6.157, <5.0, <=6.18.*, 3f2304f8c6d6ed97849057bd16fee99e434ca796, <=7.2.*, <=*, <832a685efeb5d925ee7d30011d2dbe45f81447a3, <=5.15.*, <99066cf9bba175f610ceb61a35f6fc9fbc33ff65, 6.18.50, 6.12.109, <aa107e3a68f4af177d60f2d87679e7f67179a36c, 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

Rechercher une autre CVE