CVE-2026-74287

Vulnérabilité critique dans Linux (Linux)

CVSS 9.1 · Critique
EPSS 0.7%
Linux•Linux•Versions : <=6.1.*, <92e4adfee56f32a963ebb105c6cd9a1ed707262a, 6.18.40, <=6.12.*, 7.1.5, <0c674b20c9cdb54f8a46c88b4d00cadf82b8f0c0, 2.6.12, 0, <06c8bf48505f2fef265931db82d5003d302a347b, <=7.1.*, <85f54cf589163a75fa06e37d8c2a4a72824c6dd1, <2.6.12, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 6.1.178, <=5.10.*, <=6.6.*, 6.12.97, <28ba1d3c956604a89168adfb4c97cfc6c509bba5, <ed8605c6f39b9b84f9a4631db6deb25e7f1e973c, <3a44b2602d57e11e2eb85958d4cd500d14a27d9e, <=6.18.*, 5.15.212, 6.6.145, 5.10.261, <=*, <=5.15.*, 7.2, <e9361d0ca55c4af12aac09e2572852fa91046229

Description

In the Linux kernel, the following vulnerability has been resolved: sctp: validate embedded address parameter length sctp_verify_asconf() and sctp_verify_param() only validate ADD_IP, DEL_IP, and SET_PRIMARY parameters against a fixed minimum size of sizeof(struct sctp_addip_param) + sizeof(struct sctp_paramhdr). This ensures the outer parameter is large enough to contain an embedded address parameter header, but does not verify that the embedded address parameter's declared length fits within the bounds of the outer parameter. Later, sctp_process_param() and sctp_process_asconf_param() extract the embedded address parameter and pass it to af->from_addr_param(), which uses the address parameter length to parse the variable-length address payload. A malformed peer can therefore advertise an embedded address parameter length that exceeds the remaining bytes in the enclosing parameter. Validate that addr_param->p.length does not exceed the space available after the sctp_addip_param header before processing the embedded address parameter. Reject malformed parameters when the embedded address length extends beyond the enclosing parameter bounds. This prevents out-of-bounds reads when parsing malformed parameters carried in INIT or ASCONF processing paths.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <92e4adfee56f32a963ebb105c6cd9a1ed707262a, 6.18.40, <=6.12.*, 7.1.5, <0c674b20c9cdb54f8a46c88b4d00cadf82b8f0c0, 2.6.12, 0, <06c8bf48505f2fef265931db82d5003d302a347b, <=7.1.*, <85f54cf589163a75fa06e37d8c2a4a72824c6dd1, <2.6.12, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 6.1.178, <=5.10.*, <=6.6.*, 6.12.97, <28ba1d3c956604a89168adfb4c97cfc6c509bba5, <ed8605c6f39b9b84f9a4631db6deb25e7f1e973c, <3a44b2602d57e11e2eb85958d4cd500d14a27d9e, <=6.18.*, 5.15.212, 6.6.145, 5.10.261, <=*, <=5.15.*, 7.2, <e9361d0ca55c4af12aac09e2572852fa91046229) 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