CVE-2026-63890

scsi: fcoe: Reject FIP descriptors with zero fip_dlen in CVL walker

N/A
Published: July 19, 2026 at 02:55 PM UTC
Updated: July 27, 2026 at 05:57 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.30 ≤ v < 5.10.2592.6.30 ≤ v < 5.15.2102.6.30 ≤ v < 6.1.1762.6.30 ≤ v < 6.12.932.6.30 ≤ v < 6.18.352.6.30 ≤ v < 6.6.1432.6.30 ≤ v < 7.0.122.6.30 ≤ v < 7.12.6.3097c8389d54b9665c38105ea72a428a44b97ff2f6
Vendor states this is fixed in 0e3c6e5a8fc15a74dfb1e0c1df9f1da73600a81a (fixed)
Vendor states this is fixed in 14dd80a20a72ce334adcc2d67402360527065948 (fixed)
Vendor states this is fixed in 549859a1131052b07dff11a448e9f3221a40f260 (fixed)
Vendor states this is fixed in 80a0cd307205236ca28aa49bc553f58edcb9bf3a (fixed)
Vendor states this is fixed in 9eed1bd59937e6828b00d2f2dfef631d964f3636 (fixed)
Vendor states this is fixed in d179949d2175d2857d1c3a275a22bea58bcc5d36 (fixed)
Vendor states this is fixed in d537d29d51c8b808469e5adacf3e5a0092700738 (fixed)
Vendor states this is fixed in fda976f7390bb5d1e9b84ef11ebb17323038e0c6 (fixed)
Vendor states this is fixed in 2.6.30 (unaffected)
Vendor states this is fixed in 5.10.259 (unaffected)
Vendor states this is fixed in 5.15.210 (unaffected)
Vendor states this is fixed in 6.1.176 (unaffected)
Vendor states this is fixed in 6.12.93 (unaffected)
Vendor states this is fixed in 6.18.35 (unaffected)
Vendor states this is fixed in 6.6.143 (unaffected)
Vendor states this is fixed in 7.0.12 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusAWAITING ANALYSIS

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card