GHSA-C596-8CGJ-HV56
Vulnerability from github – Published: 2026-09-04 18:31 – Updated: 2026-09-04 18:31In 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.
{
"affected": [],
"aliases": [
"CVE-2026-80874"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-04T17:16:59Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\narm64: dts: renesas: ironhide: Describe inline ECC carveouts\n\nThe DBSC5 DRAM controller protects DRAM content using inline ECC.\nThe inline ECC utilizes areas of DRAM for its operation, which are\nin the DRAM address range, but must not be accessed or modified.\nDescribe the inline ECC carveout areas used by the DBSC5 controller\non this hardware as reserved-memory, which must not be accessed.\nInclude DRAM areas which are unprotected by ECC as well, those are\nparts of the DRAM which directly precede the ECC carveout.\n\nIn case of high DRAM utilization, unless the inline ECC carveouts\nare properly reserved, Linux may use and corrupt the memory used\nby the DBSC5 DRAM controller for inline ECC, which would lead to\nthe system becoming unstable.",
"id": "GHSA-c596-8cgj-hv56",
"modified": "2026-09-04T18:31:31Z",
"published": "2026-09-04T18:31:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-80874"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/6fa6ee724d8dadf392139e242ac936b5da730c4b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7cc51bb053f6b4bb17db4e10afcef3147566cb47"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.