{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-38288 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-38288 is a high-severity denial of service vulnerability in Linux kernel, published on 10 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-38288 and fix it if it is affected.\n\nWhat it is: CVE-2025-38288 is a high-severity denial of service vulnerability in Linux kernel, published on 10 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-38288 in the wild and no public exploit code.\n\nAffected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-38288/ (Markdown: https://insights.sbomify.com/CVE-2025-38288/index.md)","id":"CVE-2025-38288","markdown":"https://insights.sbomify.com/CVE-2025-38288/index.md","name":"CVE-2025-38288","record":{"aliases":["BELL-CVE-2025-38288","DEBIAN-CVE-2025-38288","GHSA-35h8-mcvx-mrm6","UBUNTU-CVE-2025-38288"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A bug in the smartpqi SCSI driver causes kernel call traces and potential instability on preemptible kernels, requiring a patch to fix.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"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:  ...","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"scsi: smartpqi: Fix smp_processor_id() call trace for preemptible kernels","id":"CVE-2025-38288","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"scsi: lpfc: Avoid potential ndlp use-after-free in dev_loss_tmo_callbk","id":"CVE-2025-38289"},"packages":[],"prev":{"headline":"IB/cm: Drop lockdep assert and WARN when freeing old msg","id":"CVE-2025-38287"},"products":["Linux"],"published":"2025-07-10","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A bug in the smartpqi SCSI driver causes kernel call traces and potential instability on preemptible kernels, requiring a patch to fix.","url":"https://insights.sbomify.com/CVE-2025-38288/"}