# CVE-2026-74526: scsi: mpi3mr: Fix potential deadlock in mpi3mr_fault_uevent_emit

> A deadlock in the mpi3mr SCSI driver can cause a denial of service when fault handling triggers memory reclaim on blocked I/O.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-74526, GHSA-j795-hxrf-343f, UBUNTU-CVE-2026-74526

## What is CVE-2026-74526?

CVE-2026-74526 is a denial of service vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-74526?


## How do I fix CVE-2026-74526?

Apply the vendor's patch.

## Is CVE-2026-74526 being exploited?

There is no known exploitation of CVE-2026-74526 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74526 and fix it if it is affected.

What it is: CVE-2026-74526 is a denial of service vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74526 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-74526/ (Markdown: https://insights.sbomify.com/CVE-2026-74526/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-74526
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-74526
- OSV: https://osv.dev/vulnerability/CVE-2026-74526

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-74526/
Summaries are generated and may contain mistakes; the official description above is the record.