CVE-2023-53530: 
Linux Kernel vulnerability analysis and mitigation

CVE-2023-53530 is a denial-of-service vulnerability in the Linux kernel's qla2xxx SCSI driver, caused by an improper call to smp_processor_id() from preemptible code context in the qla_nvme_post_cmd() function. It affects Linux kernel versions from 6.3 up to (excluding) 6.5.5, and 6.6-rc1. The vulnerability was published on October 1, 2025, with patches backported to stable branches including 5.15.134+ and 6.1.56+. It carries a CVSS v3.1 base score of 5.5 (Medium) (Feedly, kernel.org patches).

The root cause is an incorrect use of smp_processor_id() — a function that must only be called from non-preemptible contexts — within the qla_nvme_post_cmd() function of the qla2xxx driver (CWE: NVD-CWE-noinfo / Insufficient Information). When CONFIG_DEBUG_PREEMPT is enabled in the kernel build, this misuse triggers a kernel BUG warning because the kernel can reschedule the calling task to a different CPU between the function call and its return, producing incorrect CPU ID results. The fix replaces smp_processor_id() with raw_smp_processor_id() and substitutes queue_work_on() with queue_work() throughout the driver to eliminate the unsafe pattern entirely (Feedly, kernel.org patches).

Successful exploitation results in a denial-of-service condition affecting system availability, with no impact on confidentiality or integrity. On systems with CONFIG_DEBUG_PREEMPT enabled, the kernel generates a BUG warning that can halt or degrade operations during NVMe-over-Fibre Channel (NVME-FC) device initialization and asynchronous event processing. On production systems without CONFIG_DEBUG_PREEMPT, the bug may cause incorrect CPU scheduling decisions in the driver's NVMe command posting path, potentially leading to storage subsystem instability (Feedly).

There is no known public proof-of-concept exploit and no evidence of in-the-wild exploitation for CVE-2023-53530. The vulnerability requires local access with low privileges (e.g., a local user or process able to trigger NVME-FC operations), limiting its attack surface. The EPSS score is approximately 0.018% (0.000180), indicating a very low probability of exploitation in the near term. This CVE is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog (Feedly).

• Logs: Kernel log entries containing BUG: using smp_processor_id() in preemptible [00000000] code originating from kworker processes.
• Logs: Call traces in kernel logs referencing qla_nvme_post_cmd+0x216/0x1380 [qla2xxx] and check_preemption_disabled.
• Logs: Messages indicating nvme nvme0: NVME-FC{0}: controller connect complete immediately preceding the BUG warning, suggesting the trigger occurs during NVMe-FC controller initialization.
• Process: Unusual kernel worker thread (kworker/u*) activity associated with the nvme-wq workqueue during storage operations.

Update the Linux kernel to a patched version: 6.5.5 or later (for the 6.x branch), 6.6-rc2 or later, 5.15.134 or later (for the 5.15 LTS branch), or 6.1.56 or later (for the 6.1 LTS branch). Patches are available via the stable kernel tree at git.kernel.org. As a temporary workaround for systems that cannot be patched immediately, disabling CONFIG_DEBUG_PREEMPT in the kernel build configuration will suppress the BUG warning, though this removes the detection mechanism rather than fixing the underlying scheduling issue. Prioritize patching systems that use NVME-over-Fibre Channel storage connections or have debug kernel configurations enabled (Feedly, kernel.org patches).