# CVE-2026-74352: of: reserved_mem: avoid post-init UAF when alloc_reserved_mem_array() fails

> A use-after-free vulnerability in the Linux kernel's reserved memory handling allows attackers to cause a denial of service or potentially execute code.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-74352, DEBIAN-CVE-2026-74352, GHSA-9fvr-rjg6-fvw4, UBUNTU-CVE-2026-74352

## What is CVE-2026-74352?

CVE-2026-74352 is an use after free vulnerability in Linux, published on 15 Aug 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

of: reserved_mem: avoid post-init UAF when alloc_reserved_mem_array() fails

The global pointer 'reserved_mem' continues to reference the
reserved_mem_array which lives in __initdata if
alloc_reserved_mem_array() fails. of_reserved_mem_lookup() is
exported for post-init use, that would dereference freed memory
and trigger a use-after-free.

So reset reserved_mem_count to 0 when alloc_reserved_mem_array()
fails.

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


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

Apply the vendor's patch.

## Is CVE-2026-74352 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74352 is an use after free vulnerability in Linux, published on 15 Aug 2026. 
Exploitation: There is no known exploitation of CVE-2026-74352 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-74352/ (Markdown: https://insights.sbomify.com/CVE-2026-74352/index.md)
```

## Sources

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

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