GHSA-QHPH-J75Q-5546
Vulnerability from github – Published: 2026-09-11 21:31 – Updated: 2026-09-13 09:32In the Linux kernel, the following vulnerability has been resolved:
cxl/ras: Fix cxl_rch_get_aer_info() out-of-bounds AER register read
cxl_rch_get_aer_info() copies the RCH Downstream Port AER capability from the RCRB MMIO block using a readl() loop bounded by sizeof(struct aer_capability_regs). This struct is a software layout and its embedded struct pcie_tlp_log is larger than the on-wire AER capability. As a result the loop reads past the mapped AER register block.
The over-read also populates the software-only tail fields including header_log.header_len. An out-of-range header_len passed to pcie_print_tlp_log() can then loop past the header log buffer and cause a second out-of-bounds read.
The read was correct when introduced, but struct pcie_tlp_log has since grown (Header Log and TLP Prefix Log sizes, header_len and flit fields), so sizeof(struct aer_capability_regs) no longer matches the physical AER capability.
Bound the read to the physical AER registers, header through the 16 byte Header Log. Zero the destination first so the software-only fields are deterministic.
{
"affected": [],
"aliases": [
"CVE-2026-89731"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-11T20:20:03Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ncxl/ras: Fix cxl_rch_get_aer_info() out-of-bounds AER register read\n\ncxl_rch_get_aer_info() copies the RCH Downstream Port AER capability from\nthe RCRB MMIO block using a readl() loop bounded by sizeof(struct\naer_capability_regs). This struct is a software layout and its embedded\nstruct pcie_tlp_log is larger than the on-wire AER capability. As a\nresult the loop reads past the mapped AER register block.\n\nThe over-read also populates the software-only tail fields including\nheader_log.header_len. An out-of-range header_len passed to\npcie_print_tlp_log() can then loop past the header log buffer and cause\na second out-of-bounds read.\n\nThe read was correct when introduced, but struct pcie_tlp_log has since\ngrown (Header Log and TLP Prefix Log sizes, header_len and flit fields),\nso sizeof(struct aer_capability_regs) no longer matches the physical AER\ncapability.\n\nBound the read to the physical AER registers, header through the 16 byte\nHeader Log. Zero the destination first so the software-only fields are\ndeterministic.",
"id": "GHSA-qhph-j75q-5546",
"modified": "2026-09-13T09:32:29Z",
"published": "2026-09-11T21:31:38Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89731"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/29458e62d0829cbc99435f3e44fd560f9bbf1da7"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8bd3523df1319edc61cd391e695c84a4618516df"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8e3d9dbb25d3ddbe72b4542ec4f7c4e622fe0ced"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H",
"type": "CVSS_V3"
}
]
}
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.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.