fkie_cve-2025-38288
Vulnerability from fkie_nvd
Published
2025-07-10 08:15
Modified
2025-07-10 13:17
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: scsi: smartpqi: Fix smp_processor_id() call trace for preemptible kernels Correct kernel call trace when calling smp_processor_id() when called in preemptible kernels by using raw_smp_processor_id(). smp_processor_id() checks to see if preemption is disabled and if not, issue an error message followed by a call to dump_stack(). Brief example of call trace: kernel: check_preemption_disabled: 436 callbacks suppressed kernel: BUG: using smp_processor_id() in preemptible [00000000] code: kworker/u1025:0/2354 kernel: caller is pqi_scsi_queue_command+0x183/0x310 [smartpqi] kernel: CPU: 129 PID: 2354 Comm: kworker/u1025:0 kernel: ... kernel: Workqueue: writeback wb_workfn (flush-253:0) kernel: Call Trace: kernel: <TASK> kernel: dump_stack_lvl+0x34/0x48 kernel: check_preemption_disabled+0xdd/0xe0 kernel: pqi_scsi_queue_command+0x183/0x310 [smartpqi] kernel: ...
Impacted products
Vendor Product Version



{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: smartpqi: Fix smp_processor_id() call trace for preemptible kernels\n\nCorrect kernel call trace when calling smp_processor_id() when called in\npreemptible kernels by using raw_smp_processor_id().\n\nsmp_processor_id() checks to see if preemption is disabled and if not,\nissue an error message followed by a call to dump_stack().\n\nBrief example of call trace:\nkernel:  check_preemption_disabled: 436 callbacks suppressed\nkernel:  BUG: using smp_processor_id() in preemptible [00000000]\n         code: kworker/u1025:0/2354\nkernel:  caller is pqi_scsi_queue_command+0x183/0x310 [smartpqi]\nkernel:  CPU: 129 PID: 2354 Comm: kworker/u1025:0\nkernel:  ...\nkernel:  Workqueue: writeback wb_workfn (flush-253:0)\nkernel:  Call Trace:\nkernel:   \u003cTASK\u003e\nkernel:   dump_stack_lvl+0x34/0x48\nkernel:   check_preemption_disabled+0xdd/0xe0\nkernel:   pqi_scsi_queue_command+0x183/0x310 [smartpqi]\nkernel:  ..."
    },
    {
      "lang": "es",
      "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: scsi: smartpqi: Corregir el seguimiento de llamadas smp_processor_id() para kernels preemptibles Corrija el seguimiento de llamadas al kernel cuando se llama a smp_processor_id() cuando se llama en kernels preemptibles mediante raw_smp_processor_id(). smp_processor_id() verifica si la preempci\u00f3n est\u00e1 deshabilitada y, si no lo est\u00e1, emite un mensaje de error seguido de una llamada a dump_stack(). Breve ejemplo de seguimiento de llamada: kernel: check_preemption_disabled: 436 devoluciones de llamada suprimidas kernel: ERROR: uso de smp_processor_id() en c\u00f3digo preemptible [00000000]: kworker/u1025:0/2354 kernel: el llamador es pqi_scsi_queue_command+0x183/0x310 [smartpqi] kernel: CPU: 129 PID: 2354 Comm: kworker/u1025:0 kernel: ... kernel: Workqueue: escritura diferida wb_workfn (flush-253:0) kernel: Seguimiento de llamada: kernel:  kernel: dump_stack_lvl+0x34/0x48 kernel: check_preemption_disabled+0xdd/0xe0 kernel: pqi_scsi_queue_command+0x183/0x310 [smartpqi] n\u00facleo: ..."
    }
  ],
  "id": "CVE-2025-38288",
  "lastModified": "2025-07-10T13:17:30.017",
  "metrics": {},
  "published": "2025-07-10T08:15:27.340",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/31224199316f488c8385c5dcdccf7bd80f675b81"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/42d033cf4b517e91c187ad2fbd7b30fdc6d2d62c"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/6589bc3699bcb45b35b3095c44a5af7a4d75ef7e"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Awaiting Analysis"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…

Loading…