GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel fnic: sleeping allocation under an IRQ-safe spinlock during FCoE VLAN discovery

UnscoredCVE-2026-89514Kernel, userspace & hypervisorcurated

Impact

fnic_fcoe_process_vlan_resp() allocated a VLAN descriptor with GFP_KERNEL while holding vlans_lock via spin_lock_irqsave(), so the allocation could sleep in atomic context. In practice that means a sleeping-from-invalid-context splat and, if the allocator actually blocks, a deadlock on the storage path of the node. On a GPU node this lands on the FCoE HBA used to reach shared storage, so the failure mode is a host that hangs or loses its storage path rather than a clean degradation, and the node has to be drained and rebooted. Only hosts using Cisco VIC adapters with FCoE are affected; the record gives no CVSS score and no evidence of exploitation.

Who can reach it

Reachable from the FCoE fabric the adapter is attached to: VLAN discovery responses processed by the driver. No host authentication is involved, but the sender must be on the FCoE/FIP broadcast domain. Hosts without a Cisco VIC FCoE adapter do not run this code.

What to do

Update to a kernel carrying the GFP_ATOMIC fix (commits linked in the record) and reboot each affected node; there is no runtime mitigation short of not using FCoE on the VIC. On a GPU fleet this is a rolling drain and reboot, and the storage path is in use during boot, so module reload is not a practical substitute.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.