{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93823 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93823 is a denial of service vulnerability in Linux, published on 24 Sep 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-93823 and fix it if it is affected.\n\nWhat it is: CVE-2026-93823 is a denial of service vulnerability in Linux, published on 24 Sep 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-93823 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-93823/ (Markdown: https://insights.sbomify.com/CVE-2026-93823/index.md)","id":"CVE-2026-93823","markdown":"https://insights.sbomify.com/CVE-2026-93823/index.md","name":"CVE-2026-93823","record":{"aliases":["AZL-103685","BELL-CVE-2026-93823","DEBIAN-CVE-2026-93823","GHSA-qq85-p63r-6hwh","UBUNTU-CVE-2026-93823"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker with render-group access can trigger a kernel out-of-memory condition via the AMDKFD_IOC_GET_DMABUF_INFO ioctl by specifying a large buffer size.","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/amdkfd: Let driver decide buffer size at AMDKFD_IOC_GET_DMABUF_INFO ioctl\n\namdkfd driver needs allocate buffer to return bo metadata to user space. The\nbuffer size is controlled by user currently. It is a potential security issue\nthat hostile value (e.g. 2 GiB) lets any render-group user trigger order-MAX\nallocation/OOM in kernel context.\n\nThis patch first finds bo metadata size. If the size is smaller than user\nprovided value drive can safely allocate buffer in kernel space and copy to\nuser space buffer. If not, driver will let user know, not allocate and copy.\nUser will redo with new buffer in user space.\n\nThis patch lets driver decide buffer allocation size to avoid potential hostile\nsize from user space.\n\n(cherry picked from commit f54ce9e8cbd3abe0eda3a285f54dc4f572fe589a)","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/amdkfd: Let driver decide buffer size at AMDKFD_IOC_GET_DMABUF_INFO ioctl","id":"CVE-2026-93823","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":"tls: reject the combination of TLS and sockmap","id":"CVE-2026-93824"},"packages":[],"prev":{"headline":"PCI: iproc: Protect root bus removal with rescan lock","id":"CVE-2026-93822"},"products":["Linux"],"published":"2026-09-24","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-03","vendors":["Linux"]},"summary":"A local attacker with render-group access can trigger a kernel out-of-memory condition via the AMDKFD_IOC_GET_DMABUF_INFO ioctl by specifying a large buffer size.","url":"https://insights.sbomify.com/CVE-2026-93823/"}