CVE-2026-74526: scsi: mpi3mr: Fix potential deadlock in mpi3mr_fault_uevent_emit
Greg Kroah-Hartman <[email protected]>
| Newsgroups | org.kernel.vger.linux-cve-announce |
|---|---|
| Message-ID | <2026081545-CVE-2026-74526-09fd@gregkh> |
From: Greg Kroah-Hartman <[email protected]> Description =========== In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Fix potential deadlock in mpi3mr_fault_uevent_emit mpi3mr_fault_uevent_emit() runs from the fault watchdog and reset paths where host I/O may already be blocked. GFP_KERNEL allocations here, both the local kzalloc_obj() and the ones inside kobject_uevent_env() itself, can trigger reclaim that waits on that blocked I/O and deadlock. Use memalloc_noio_save()/restore() to cover the whole call instead of just the local allocation. The Linux kernel CVE team has assigned CVE-2026-74526 to this issue. Affected and fixed versions =========================== Issue introduced in 7.0 with commit ec54b348f274fdd2bd32bbe74de6d62ae1a10a18 and fixed in 7.1.8 with commit df817b19dac7034416d18f14347010b3e9f5cf3d Issue introduced in 7.0 with commit ec54b348f274fdd2bd32bbe74de6d62ae1a10a18 and fixed in 7.2-rc6 with commit ccff8c92571500fcfed21281e33daaf645bf692f Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-74526 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/scsi/mpi3mr/mpi3mr_fw.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/df817b19dac7034416d18f14347010b3e9f5cf3d https://git.kernel.org/stable/c/ccff8c92571500fcfed21281e33daaf645bf692f