{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-43347 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-43347 is a high-severity denial of service vulnerability in Linux kernel, published on 8 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-43347 and fix it if it is affected.\n\nWhat it is: CVE-2026-43347 is a high-severity denial of service vulnerability in Linux kernel, published on 8 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-43347 in the wild and no public exploit code.\n\nAffected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-43347/ (Markdown: https://insights.sbomify.com/CVE-2026-43347/index.md)","id":"CVE-2026-43347","markdown":"https://insights.sbomify.com/CVE-2026-43347/index.md","name":"CVE-2026-43347","record":{"aliases":["BELL-CVE-2026-43347","DEBIAN-CVE-2026-43347","GHSA-m2rg-757j-v6hh","UBUNTU-CVE-2026-43347"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"Kernel crashes occur on Qualcomm Monaco platforms due to improper memory reservation, allowing access to hypervisor-owned memory.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"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–0x91a87fff (288 KiB). The remaining portion\n(0x91a88000–0x91afffff) 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","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"arm64: dts: qcom: monaco: Reserve full Gunyah metadata region","id":"CVE-2026-43347","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"mshv_vtl: Fix vmemmap_shift exceeding MAX_FOLIO_ORDER","id":"CVE-2026-43348"},"packages":[],"prev":{"headline":"ice: ptp: don't WARN when controlling PF is unavailable","id":"CVE-2026-43346"},"products":["Linux"],"published":"2026-05-08","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-05","vendors":["Linux"]},"summary":"Kernel crashes occur on Qualcomm Monaco platforms due to improper memory reservation, allowing access to hypervisor-owned memory.","url":"https://insights.sbomify.com/CVE-2026-43347/"}