GHSA-M2RG-757J-V6HH
Vulnerability from github – Published: 2026-05-08 15:31 – Updated: 2026-05-11 09:30In the Linux kernel, the following vulnerability has been resolved:
arm64: dts: qcom: monaco: Reserve full Gunyah metadata region
We observe spurious "Synchronous External Abort" exceptions (ESR=0x96000010) and kernel crashes on Monaco-based platforms. These faults are caused by the kernel inadvertently accessing hypervisor-owned memory that is not properly marked as reserved.
From boot log, The Qualcomm hypervisor reports the memory range at 0x91a80000 of size 0x80000 (512 KiB) as hypervisor-owned: qhee_hyp_assign_remove_memory: 0x91a80000/0x80000 -> ret 0
However, the EFI memory map provided by firmware only reserves the subrange 0x91a40000–0x91a87fff (288 KiB). The remaining portion (0x91a88000–0x91afffff) is incorrectly reported as conventional memory (from efi debug): efi: 0x000091a40000-0x000091a87fff [Reserved...] efi: 0x000091a88000-0x0000938fffff [Conventional...]
As a result, the allocator may hand out PFNs inside the hypervisor owned region, causing fatal aborts when the kernel accesses those addresses.
Add a reserved-memory carveout for the Gunyah hypervisor metadata at 0x91a80000 (512 KiB) and mark it as no-map so Linux does not map or allocate from this area.
For the record: Hyp version: gunyah-e78adb36e debug (2025-11-17 05:38:05 UTC) UEFI Ver: 6.0.260122.BOOT.MXF.1.0.c1-00449-KODIAKLA-1
{
"affected": [],
"aliases": [
"CVE-2026-43347"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-05-08T14:16:44Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\narm64: dts: qcom: monaco: Reserve full Gunyah metadata region\n\nWe observe spurious \"Synchronous External Abort\" exceptions\n(ESR=0x96000010) and kernel crashes on Monaco-based platforms.\nThese faults are caused by the kernel inadvertently accessing\nhypervisor-owned memory that is not properly marked as reserved.\n\n\u003eFrom boot log, The Qualcomm hypervisor reports the memory range\nat 0x91a80000 of size 0x80000 (512 KiB) as hypervisor-owned:\nqhee_hyp_assign_remove_memory: 0x91a80000/0x80000 -\u003e ret 0\n\nHowever, the EFI memory map provided by firmware only reserves the\nsubrange 0x91a40000\u20130x91a87fff (288 KiB). The remaining portion\n(0x91a88000\u20130x91afffff) is incorrectly reported as conventional\nmemory (from efi debug):\nefi: 0x000091a40000-0x000091a87fff [Reserved...]\nefi: 0x000091a88000-0x0000938fffff [Conventional...]\n\nAs a result, the allocator may hand out PFNs inside the hypervisor\nowned region, causing fatal aborts when the kernel accesses those\naddresses.\n\nAdd a reserved-memory carveout for the Gunyah hypervisor metadata\nat 0x91a80000 (512 KiB) and mark it as no-map so Linux does not\nmap or allocate from this area.\n\nFor the record:\nHyp version: gunyah-e78adb36e debug (2025-11-17 05:38:05 UTC)\nUEFI Ver: 6.0.260122.BOOT.MXF.1.0.c1-00449-KODIAKLA-1",
"id": "GHSA-m2rg-757j-v6hh",
"modified": "2026-05-11T09:30:30Z",
"published": "2026-05-08T15:31:24Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-43347"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/59bd9088336d2bb7e713dcf4df5cbda86bb3c611"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/85d98669fa7f1d3041d962515e45ee6e392db6f8"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/edde62571f7602d83243ca51729ce42d22ea04d2"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.