Heimdall Security Logo

CVE-2026-63890

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <14dd80a20a72ce334adcc2d67402360527065948, <=6.1.*, <=7.0.*, <=6.12.*, 6.12.93, <d537d29d51c8b808469e5adacf3e5a0092700738, 0, 6.18.35, 6.1.176, 5.15.210, <=5.10.*, 2.6.30, <d179949d2175d2857d1c3a275a22bea58bcc5d36, <=6.6.*, <fda976f7390bb5d1e9b84ef11ebb17323038e0c6, <2.6.30, 7.1, <=6.18.*, <9eed1bd59937e6828b00d2f2dfef631d964f3636, 7.0.12, <=*, <=5.15.*, <0e3c6e5a8fc15a74dfb1e0c1df9f1da73600a81a, <80a0cd307205236ca28aa49bc553f58edcb9bf3a, 6.6.143, <549859a1131052b07dff11a448e9f3221a40f260, 97c8389d54b9665c38105ea72a428a44b97ff2f6, 5.10.259

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: fcoe: Reject FIP descriptors with zero fip_dlen in CVL walker drivers/scsi/fcoe/fcoe_ctlr.c::fcoe_ctlr_recv_clr_vlink() advanced the descriptor cursor by an attacker-supplied fip_dlen without ever requiring dlen >= sizeof(struct fip_desc) in the default branch. The named descriptor cases (FIP_DT_MAC, FIP_DT_NAME, FIP_DT_VN_ID) checked their per-type minimum lengths, but a FIP_DT_NON_CRITICAL descriptor (fip_dtype >= 128, which the standard requires receivers to silently ignore) skipped that check entirely. An unauthenticated L2 peer on the FCoE control VLAN could hang fcoe_ctlr_recv_work on an fcoe, qedf, or bnx2fc initiator indefinitely by emitting one FIP CVL frame whose single descriptor had fip_dtype == FIP_DT_NON_CRITICAL and fip_dlen == 0: the cursor advanced zero bytes per iteration and the loop condition rlen >= sizeof(*desc) stayed true forever, blocking every subsequent FIP frame on that controller. Tighten the outer dlen guard to also reject dlen < sizeof(struct fip_desc), so a malformed descriptor whose length cannot even cover the descriptor header is rejected before the switch. This is the same lower-bound the named cases already apply and is the minimum scope that closes the loop.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <14dd80a20a72ce334adcc2d67402360527065948, <=6.1.*, <=7.0.*, <=6.12.*, 6.12.93, <d537d29d51c8b808469e5adacf3e5a0092700738, 0, 6.18.35, 6.1.176, 5.15.210, <=5.10.*, 2.6.30, <d179949d2175d2857d1c3a275a22bea58bcc5d36, <=6.6.*, <fda976f7390bb5d1e9b84ef11ebb17323038e0c6, <2.6.30, 7.1, <=6.18.*, <9eed1bd59937e6828b00d2f2dfef631d964f3636, 7.0.12, <=*, <=5.15.*, <0e3c6e5a8fc15a74dfb1e0c1df9f1da73600a81a, <80a0cd307205236ca28aa49bc553f58edcb9bf3a, 6.6.143, <549859a1131052b07dff11a448e9f3221a40f260, 97c8389d54b9665c38105ea72a428a44b97ff2f6, 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