CVE-2023-53530scsi: qla2xxx: Use raw_smp_processor_id() instead of smp_processor_id()
- 5.5MediumCVSS base score
- 0.15%Exploitation in 30 daysEPSS · top 96% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
Published
- 7 months later
· 7 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.15% · top 96% of all CVEs (13 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 532a239605667320f4fd7473e416b718d0a2fbbb – < 1a541999f31fcb10ea50eba2a563e6c451fd5c7d
- affected 35c02a333d523d9da0b482b0d751cdeb95c068ae – < 52c7b41ad6ee53222f4ee2f0c099a6ed8291a168
- affected 1d201c81d4cc6840735bbcc99e6031503e5cf3b8 – < 25bd0c7def04a272f8e89b36971712fe29c6e438
- affected 1d201c81d4cc6840735bbcc99e6031503e5cf3b8 – < 59f10a05b5c7b675256a66e3161741239889ff80
- affected 6.3
- unaffected < 6.3
- unaffected 6.5.5 – ≤ 6.5.*
- unaffected 6.6 – ≤ *
References
References4
- https://git.kernel.org/stable/c/1a541999f31fcb10ea50eba2a563e6c451fd5c7d (opens in a new tab)
- https://git.kernel.org/stable/c/52c7b41ad6ee53222f4ee2f0c099a6ed8291a168 (opens in a new tab)
- https://git.kernel.org/stable/c/25bd0c7def04a272f8e89b36971712fe29c6e438 (opens in a new tab)
- https://git.kernel.org/stable/c/59f10a05b5c7b675256a66e3161741239889ff80 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-32753 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2023-53530)Record last updated .