CVE-2023-53530

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> scsi: qla2xxx: Use raw_smp_processor_id() instead of smp_processor_id()<br /> <br /> The following call trace was observed:<br /> <br /> localhost kernel: nvme nvme0: NVME-FC{0}: controller connect complete<br /> localhost kernel: BUG: using smp_processor_id() in preemptible [00000000] code: kworker/u129:4/75092<br /> localhost kernel: nvme nvme0: NVME-FC{0}: new ctrl: NQN "nqn.1992-08.com.netapp:sn.b42d198afb4d11ecad6d00a098d6abfa:subsystem.PR_Channel2022_RH84_subsystem_291"<br /> localhost kernel: caller is qla_nvme_post_cmd+0x216/0x1380 [qla2xxx]<br /> 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<br /> localhost kernel: Hardware name: HPE ProLiant XL420 Gen10/ProLiant XL420 Gen10, BIOS U39 01/13/2022<br /> localhost kernel: Workqueue: nvme-wq nvme_async_event_work [nvme_core]<br /> localhost kernel: Call Trace:<br /> localhost kernel: dump_stack_lvl+0x57/0x7d<br /> localhost kernel: check_preemption_disabled+0xc8/0xd0<br /> localhost kernel: qla_nvme_post_cmd+0x216/0x1380 [qla2xxx]<br /> <br /> Use raw_smp_processor_id() instead of smp_processor_id().<br /> <br /> Also use queue_work() across the driver instead of queue_work_on() thus<br /> avoiding usage of smp_processor_id() when CONFIG_DEBUG_PREEMPT is enabled.