LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53530: scsi: qla2xxx: Use raw_smp_processor_id() instead of smp_processor_id()

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Use raw_smp_processor_id() instead of smp_processor_id() The following call trace was observed: localhost kernel: nvme nvme0: NVME-FC{0}: controller connect complete localhost kernel: BUG: using smp_processor_id() in preemptible [00000000] code: kworker/u129:4/75092 localhost kernel: nvme nvme0: NVME-FC{0}: new ctrl: NQN "nqn.1992-08.com.netapp:sn.b42d198afb4d11ecad6d00a098d6abfa:subsystem.PR_Channel2022_RH84_subsystem_291" localhost kernel: caller is qla_nvme_post_cmd+0x216/0x1380 [qla2xxx] localhost kernel: CPU: 6 PID: 75092 Comm: kworker/u129:4 Kdump: loaded Tainted: G B W OE --------- --- 5.14.0-70.22.1.el9_0.x86_64+debug #1 localhost kernel: Hardware name: HPE ProLiant XL420 Gen10/ProLiant XL420 Gen10, BIOS U39 01/13/2022 localhost kernel: Workqueue: nvme-wq nvme_async_event_work [nvme_core] localhost kernel: Call Trace: localhost kernel: dump_stack_lvl+0x57/0x7d localhost kernel: check_preemption_disabled+0xc8/0xd0 localhost kernel: qla_nvme_post_cmd+0x216/0x1380 [qla2xxx] Use raw_smp_processor_id() instead of smp_processor_id(). Also use queue_work() across the driver instead of queue_work_on() thus avoiding usage of smp_processor_id() when CONFIG_DEBUG_PREEMPT is enabled.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2023-53530 is a Linux kernel qla2xxx Fibre Channel/NVMe-FC driver issue. The public record describes a kernel BUG warning from using smp_processor_id() in preemptible code. It was resolved by changing CPU-id and workqueue handling. No CVSS score, CWE, or confirmed exploitation is provided.

Executive priority

Treat this as a targeted kernel maintenance item for storage-heavy Linux environments, not a broad emergency. Prioritize validation where qla2xxx Fibre Channel hardware supports critical workloads.

Technical view

The qla2xxx driver hit check_preemption_disabled() from qla_nvme_post_cmd() when CONFIG_DEBUG_PREEMPT was enabled. The fix uses raw_smp_processor_id() and queue_work() instead of queue_work_on() across the driver. Source data lists Linux as affected and references stable kernel commits, but distro-specific impact requires vendor mapping.

Likely exposure

Exposure is most likely on Linux systems using the qla2xxx SCSI/Fibre Channel driver with NVMe-FC workloads. The source bundle lists Linux versions and commits, but does not provide a clean product matrix for distributions or appliances.

Exploitation context

The bundle does not cite active exploitation, public exploit code, KEV listing, or a practical attacker path. Evidence is limited to a kernel call trace and the upstream stable fixes.

Researcher notes

Impact details are incomplete: no CVSS, CWE, attacker model, or exploitability statement is supplied. The strongest evidence is the upstream fix and observed BUG trace under CONFIG_DEBUG_PREEMPT.

Mitigation direction

  • Check your kernel vendor advisory for CVE-2023-53530 applicability.
  • Upgrade to a vendor kernel containing the referenced stable fixes.
  • Prioritize systems using qla2xxx Fibre Channel or NVMe-FC paths.
  • Review storage appliance or distribution backports before assuming exposure.

Validation and detection

  • Inventory Linux hosts loading the qla2xxx kernel module.
  • Identify kernel versions and vendor backport status.
  • Search kernel logs for matching DEBUG_PREEMPT BUG traces.
  • Confirm patched kernels include the referenced stable commits.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-53530 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux532a239605667320f4fd7473e416b718d0a2fbbb, 35c02a333d523d9da0b482b0d751cdeb95c068ae, 1d201c81d4cc6840735bbcc99e6031503e5cf3b8, 1d201c81d4cc6840735bbcc99e6031503e5cf3b8unaffected
LinuxLinux6.3, 0, 6.5.5, 6.6affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.