Heimdall Security Logo

CVE-2026-46064

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : 7.0.4, <=6.1.*, <=7.0.*, <=6.12.*, <fd19eb1c75047a4ed4e855f56cafd704dc3914e0, <ca1c857e2bb74a9fc0606128334f85316d57067b, 2.6.12, 0, 6.18.27, <2.6.12, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, <ce57fa439bd1b5d664f334a0c3e3f0e42abb0153, 5.15.209, <9aad71144fa3682cca3837a06c8623016790e7ec, <=5.10.*, <=6.6.*, 6.1.175, <b870f652877bfbe321bd0f4096fc37a93296f7b6, 7.1, <=6.18.*, 5.10.258, <fe31722b0194ff76bf8b461e8bf97a2081147787, <c1c2417c60dbdca5ebb00462f21ee71c2d7f7083, <=*, <=5.15.*, <9e8f6c9d4ecddda2f28baa1678340286cff3969c, 6.6.140, 6.12.86

Description

In the Linux kernel, the following vulnerability has been resolved: ibmasm: fix heap over-read in ibmasm_send_i2o_message() The ibmasm_send_i2o_message() function uses get_dot_command_size() to compute the byte count for memcpy_toio(), but this value is derived from user-controlled fields in the dot_command_header (command_size: u8, data_size: u16) and is never validated against the actual allocation size. A root user can write a small buffer with inflated header fields, causing memcpy_toio() to read up to ~65 KB past the end of the allocation into adjacent kernel heap, which is then forwarded to the service processor over MMIO. Silently clamping the copy size is not sufficient: if the header fields claim a larger size than the buffer, the SP receives a dot command whose own header is inconsistent with the I2O message length, which can cause the SP to desynchronize. Reject such commands outright by returning failure. Validate command_size before calling get_mfa_inbound() to avoid leaking an I2O message frame: reading INBOUND_QUEUE_PORT dequeues a hardware frame from the controller's free pool, and returning without a corresponding set_mfa_inbound() call would permanently exhaust it. Additionally, clamp command_size to I2O_COMMAND_SIZE before the memcpy_toio() so the MMIO write stays within the I2O message frame, consistent with the clamping already performed by outgoing_message_size() for the header field.

Gravité et risque d'exploitation

CVE-2026-46064 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.17 %, ce qui la place devant 5.9 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 7.0.4, <=6.1.*, <=7.0.*, <=6.12.*, <fd19eb1c75047a4ed4e855f56cafd704dc3914e0, <ca1c857e2bb74a9fc0606128334f85316d57067b, 2.6.12, 0, 6.18.27, <2.6.12, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, <ce57fa439bd1b5d664f334a0c3e3f0e42abb0153, 5.15.209, <9aad71144fa3682cca3837a06c8623016790e7ec, <=5.10.*, <=6.6.*, 6.1.175, <b870f652877bfbe321bd0f4096fc37a93296f7b6, 7.1, <=6.18.*, 5.10.258, <fe31722b0194ff76bf8b461e8bf97a2081147787, <c1c2417c60dbdca5ebb00462f21ee71c2d7f7083, <=*, <=5.15.*, <9e8f6c9d4ecddda2f28baa1678340286cff3969c, 6.6.140, 6.12.86) 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