{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68436 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68436 is a denial of service vulnerability in Linux, published on 12 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-68436 and fix it if it is affected.\n\nWhat it is: CVE-2026-68436 is a denial of service vulnerability in Linux, published on 12 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-68436 in the wild and no public exploit code.\n\nAffected product: Linux. 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-68436/ (Markdown: https://insights.sbomify.com/CVE-2026-68436/index.md)","id":"CVE-2026-68436","markdown":"https://insights.sbomify.com/CVE-2026-68436/index.md","name":"CVE-2026-68436","record":{"aliases":["BELL-CVE-2026-68436","DEBIAN-CVE-2026-68436","GHSA-7q8m-jhfw-frrf","UBUNTU-CVE-2026-68436"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A kernel bug causes AMD GPU display initialization to fail if the driver structure exceeds memory limits, resulting in a denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: use kvzalloc to allocate struct dc\n\nstruct dc has grown large over time (most of it the two inlined\ndc_scratch_space copies) and now sits close to the page allocator's 4 MiB\ncontiguous allocation limit. Its actual size is not fixed by the source\nalone, it also depends on the compiler and the .config, so it can easily\ncross 4 MiB, e.g. with a newer GCC or a config change.\n\ndc_create() allocates it with kzalloc(). Once struct dc exceeds 4 MiB the\nrequest is rounded up to order 11 (8 MiB), which is above MAX_PAGE_ORDER,\nso the page allocator warns and returns NULL. dc_create() then fails, DM\ninit fails and amdgpu probe aborts with -EINVAL:\n\n  WARNING: mm/page_alloc.c:5197 at __alloc_frozen_pages_noprof+0x2f9/0x380\n   dc_create+0x38/0x660 [amdgpu]\n   amdgpu_dm_init+0x2d9/0x510 [amdgpu]\n   dm_hw_init+0x1b/0x90 [amdgpu]\n   amdgpu_device_init.cold+0x150d/0x1e13 [amdgpu]\n   amdgpu_driver_load_kms+0x19/0x80 [amdgpu]\n   amdgpu_pci_probe+0x1e2/0x4c0 [amdgpu]\n\ndc_create() then returns NULL and DM init fails, which aborts the whole\nGPU init and makes amdgpu probe fail with -EINVAL (\"hw_init of IP block\n\u003cdm\u003e failed -22\"), leaving the display unusable. The subsequent\namdgpu_irq_put() warnings during teardown are just fallout of unwinding\na half-initialized device.\n\nstruct dc is a software-only bookkeeping structure that is never handed\nto hardware DMA and is only ever kept as an opaque pointer, so it does\nnot require physically contiguous memory. Allocate it with kvzalloc()\n(and free it with kvfree()) so that the allocator can fall back to\nvmalloc() when a contiguous allocation of that size is not available,\nwhich also avoids the MAX_PAGE_ORDER warning entirely.\n\nv2:\n - Rebase to amd-staging-drm-next.\n\n(cherry picked from commit 991e0516a8072f2292681c6ae98a924ab0e32575)","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":"drm/amd/display: use kvzalloc to allocate struct dc","id":"CVE-2026-68436","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"drm/imagination: Fit paired fragment job in the correct CCCB","id":"CVE-2026-68437"},"packages":[],"prev":{"headline":"LoongArch: Fix address space mismatch in kexec command line lookup","id":"CVE-2026-68435"},"products":["Linux"],"published":"2026-08-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"A kernel bug causes AMD GPU display initialization to fail if the driver structure exceeds memory limits, resulting in a denial of service.","url":"https://insights.sbomify.com/CVE-2026-68436/"}