CVE-2026-63890
CVE CVE-2026-63890EUVD EUVD-2026-45663Published 2026-07-19T14:55:02.000Z
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 5.10.259; patch: 6.6.143; 97c8389d54b9665c38105ea72a428a44b97ff2f6 <0e3c6e5a8fc15a74dfb1e0c1df9f1da73600a81a; 97c8389d54b9665c38105ea72a428a44b97ff2f6 <d179949d2175d2857d1c3a275a22bea58bcc5d36; 97c8389d54b9665c38105ea72a428a44b97ff2f6 <d537d29d51c8b808469e5adacf3e5a0092700738; patch: 6.12.93; 97c8389d54b9665c38105ea72a428a44b97ff2f6 <9eed1bd59937e6828b00d2f2dfef631d964f3636; patch: 0; patch: 6.18.35; 97c8389d54b9665c38105ea72a428a44b97ff2f6 <549859a1131052b07dff11a448e9f3221a40f260; 97c8389d54b9665c38105ea72a428a44b97ff2f6 <80a0cd307205236ca28aa49bc553f58edcb9bf3a; patch: 6.1.176; 97c8389d54b9665c38105ea72a428a44b97ff2f6 <14dd80a20a72ce334adcc2d67402360527065948; 97c8389d54b9665c38105ea72a428a44b97ff2f6 <fda976f7390bb5d1e9b84ef11ebb17323038e0c6; 2.6.30; patch: 5.15.210; patch: 7.1; patch: 7.0.12
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.