# CVE-2026-80874: arm64: dts: renesas: ironhide: Describe inline ECC carveouts

> Improper memory reservation for inline ECC carveouts in the Linux kernel can lead to system instability and denial of service under high DRAM utilization.

- **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:** 4 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-80874, GHSA-c596-8cgj-hv56, UBUNTU-CVE-2026-80874

## What is CVE-2026-80874?

CVE-2026-80874 is a memory corruption vulnerability in Linux, published on 4 Sep 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:

arm64: dts: renesas: ironhide: Describe inline ECC carveouts

The DBSC5 DRAM controller protects DRAM content using inline ECC.
The inline ECC utilizes areas of DRAM for its operation, which are
in the DRAM address range, but must not be accessed or modified.
Describe the inline ECC carveout areas used by the DBSC5 controller
on this hardware as reserved-memory, which must not be accessed.
Include DRAM areas which are unprotected by ECC as well, those are
parts of the DRAM which directly precede the ECC carveout.

In case of high DRAM utilization, unless the inline ECC carveouts
are properly reserved, Linux may use and corrupt the memory used
by the DBSC5 DRAM controller for inline ECC, which would lead to
the system becoming unstable.

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


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

Apply the vendor's patch.

## Is CVE-2026-80874 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80874 is a memory corruption vulnerability in Linux, published on 4 Sep 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-80874 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-80874/ (Markdown: https://insights.sbomify.com/CVE-2026-80874/index.md)
```

## Sources

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

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