UBUNTU-CVE-2026-89514: Medium severity ubuntu/linux-hwe-edge vulnerability
In the Linux kernel, the following vulnerability has been resolved: scsi: fnic: Use GFPATOMIC for VLAN alloc under spinlock fnicfcoeprocessvlanresp() allocates a VLAN descriptor with kzallocobj() (default GFPKERNEL) while holding vlanslock via spinlockirqsave(). GFPKERNEL may sleep, which is not allowed in this atomic context and can trigger a sleeping-from-invalid-context warning or deadlock. Pass GFPATOMIC so the allocation is safe under the IRQ-safe spinlock.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1 - Compensating control
In fnic_fcoe_process_vlan_resp(), pass GFP_ATOMIC to kzalloc_obj() when allocating the VLAN descriptor while holding vlans_lock via spin_lock_irqsave().
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
The affected software list includes Ubuntu linux-riscv, linux-realtime, linux-hwe-edge, linux-azure, linux-gcp, linux-azure-fde, linux-gke, and linux-aws-5.0 kernel packages. The issue is in the fnic SCSI driver’s VLAN response processing path.
What condition triggers the vulnerability?
The condition occurs when fnic_fcoe_process_vlan_resp() allocates a VLAN descriptor while holding an IRQ-safe spinlock. The allocation used GFP_KERNEL, which can sleep even though sleeping is not permitted in that atomic context.
What is the likely impact?
A triggered allocation can produce a sleeping-from-invalid-context warning or lead to a deadlock. The supplied information does not describe data disclosure, privilege escalation, or remote code execution.
What is the remediation?
The resolved change uses GFP_ATOMIC for the VLAN descriptor allocation, making it safe while the IRQ-safe spinlock is held. Update to an Ubuntu kernel package that includes this fix.