{"api_version":"1","generated_at":"2026-09-25T23:21:24+00:00","cve":"CVE-2026-93823","urls":{"html":"https://cve.report/CVE-2026-93823","api":"https://cve.report/api/cve/CVE-2026-93823.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-93823","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-93823"},"summary":{"title":"drm/amdkfd: Let driver decide buffer size at AMDKFD_IOC_GET_DMABUF_INFO ioctl","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)","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-24 17:17:15","updated_at":"2026-09-25 13:17:23"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/a65ccabde6deb95baf9442bd98299e2248884162","name":"https://git.kernel.org/stable/c/a65ccabde6deb95baf9442bd98299e2248884162","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/8242a8d9d7194d5ef8a8b38a5621ca0966a3ec15","name":"https://git.kernel.org/stable/c/8242a8d9d7194d5ef8a8b38a5621ca0966a3ec15","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/2d9fd0f01550aab4a0a1984b4379e50545906248","name":"https://git.kernel.org/stable/c/2d9fd0f01550aab4a0a1984b4379e50545906248","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-93823","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93823","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1dde0ea95b782425b95455d487cb44991525a1d1 a65ccabde6deb95baf9442bd98299e2248884162 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1dde0ea95b782425b95455d487cb44991525a1d1 2d9fd0f01550aab4a0a1984b4379e50545906248 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1dde0ea95b782425b95455d487cb44991525a1d1 8242a8d9d7194d5ef8a8b38a5621ca0966a3ec15 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5.0","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.0 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.111 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.53 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c","drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.h","drivers/gpu/drm/amd/amdkfd/kfd_chardev.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"a65ccabde6deb95baf9442bd98299e2248884162","status":"affected","version":"1dde0ea95b782425b95455d487cb44991525a1d1","versionType":"git"},{"lessThan":"2d9fd0f01550aab4a0a1984b4379e50545906248","status":"affected","version":"1dde0ea95b782425b95455d487cb44991525a1d1","versionType":"git"},{"lessThan":"8242a8d9d7194d5ef8a8b38a5621ca0966a3ec15","status":"affected","version":"1dde0ea95b782425b95455d487cb44991525a1d1","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c","drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.h","drivers/gpu/drm/amd/amdkfd/kfd_chardev.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"5.0"},{"lessThan":"5.0","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.111","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.53","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.111","versionStartIncluding":"5.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.53","versionStartIncluding":"5.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2","versionStartIncluding":"5.0","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"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)"}],"providerMetadata":{"dateUpdated":"2026-09-25T12:43:32.493Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/a65ccabde6deb95baf9442bd98299e2248884162"},{"url":"https://git.kernel.org/stable/c/2d9fd0f01550aab4a0a1984b4379e50545906248"},{"url":"https://git.kernel.org/stable/c/8242a8d9d7194d5ef8a8b38a5621ca0966a3ec15"}],"title":"drm/amdkfd: Let driver decide buffer size at AMDKFD_IOC_GET_DMABUF_INFO ioctl","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-93823","datePublished":"2026-09-24T16:03:01.639Z","dateReserved":"2026-09-18T17:59:28.792Z","dateUpdated":"2026-09-25T12:43:32.493Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-24 17:17:15","lastModifiedDate":"2026-09-25 13:17:23","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"93823","Ordinal":"1","Title":"drm/amdkfd: Let driver decide buffer size at AMDKFD_IOC_GET_DMAB","CVE":"CVE-2026-93823","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"93823","Ordinal":"1","NoteData":"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)","Type":"Description","Title":"drm/amdkfd: Let driver decide buffer size at AMDKFD_IOC_GET_DMAB"}]}}}