Description
In the Linux kernel, the following vulnerability has been resolved:

scsi: fnic: Use GFP_ATOMIC for VLAN alloc under spinlock

fnic_fcoe_process_vlan_resp() allocates a VLAN descriptor with
kzalloc_obj() (default GFP_KERNEL) while holding vlans_lock via
spin_lock_irqsave(). GFP_KERNEL may sleep, which is not allowed in this
atomic context and can trigger a sleeping-from-invalid-context warning
or deadlock.

Pass GFP_ATOMIC so the allocation is safe under the IRQ-safe spinlock.
Published: 2026-09-11
Score: 4.4 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Kernel stability issue
Action: Patch
AI Analysis

Impact

In the fnic driver, the function fnic_fcoe_process_vlan_resp() allocates a VLAN descriptor using kzalloc_obj() with the default GFP_KERNEL flag while holding the vlans_lock spinlock. GFP_KERNEL permits sleeping, which is disallowed in an interrupt‑safe spinlock context; the result is a sleeping‑from‑invalid‑context warning or, in worst case, a deadlock that affects kernel stability.

Affected Systems

All systems that run the Linux kernel including an unpatched fnic_fcoe_process_vlan_resp() function are affected. The vulnerability exists in any kernel build that contains this function without the fix that switches the allocation flag to GFP_ATOMIC. No specific kernel release is identified, so any kernel with the vulnerable code path is at risk.

Risk and Exploitability

The CVSS base score is 4.4, and the EPSS score is < 1%, indicating a very low likelihood of exploitation. The vulnerability is not listed in the CISA KEV catalog. Based on the description, it is inferred that exploitation would require local access to the affected system and the ability to interact with the fnic driver, making it a kernel stability issue rather than a remote code execution vector.

Generated by OpenCVE AI on September 12, 2026 at 16:24 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply a Linux kernel release that patches fnic_fcoe_process_vlan_resp() to use GFP_ATOMIC instead of GFP_KERNEL.
  • Re load the fixed driver code.
  • Monitor dmesg or system logs for "sleeping‑from‑invalid‑context" warnings and confirm they no longer appear.

Generated by OpenCVE AI on September 12, 2026 at 16:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 12 Sep 2026 16:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-749

Sat, 12 Sep 2026 12:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-663
References
Metrics threat_severity

None

cvssV3_1

{'score': 4.4, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate


Sat, 12 Sep 2026 07:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-749

Fri, 11 Sep 2026 23:45:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: scsi: fnic: Use GFP_ATOMIC for VLAN alloc under spinlock fnic_fcoe_process_vlan_resp() allocates a VLAN descriptor with kzalloc_obj() (default GFP_KERNEL) while holding vlans_lock via spin_lock_irqsave(). GFP_KERNEL may sleep, which is not allowed in this atomic context and can trigger a sleeping-from-invalid-context warning or deadlock. Pass GFP_ATOMIC so the allocation is safe under the IRQ-safe spinlock.
Title scsi: fnic: Use GFP_ATOMIC for VLAN alloc under spinlock
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-09-11T19:43:58.621Z

Reserved: 2026-09-11T19:38:34.717Z

Link: CVE-2026-89514

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-11T20:19:33.913

Modified: 2026-09-11T20:19:33.913

Link: CVE-2026-89514

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-09-11T19:43:58Z

Links: CVE-2026-89514 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-09-12T16:30:13Z

Weaknesses
  • CWE-663

    Use of a Non-reentrant Function in a Concurrent Context