{"id":"CVE-2026-93823","title":"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","summary":"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 …","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < a65ccabde6deb95baf9442bd98299e2248884162","Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 2d9fd0f01550aab4a0a1984b4379e50545906248","Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 8242a8d9d7194d5ef8a8b38a5621ca0966a3ec15","Linux < 6.12.111","Linux < 6.18.53","Linux (all versions)"],"published":"2026-09-24","updated":"2026-09-25","sourceUpdated":"2026-09-25T13:17:23.130","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-93823","references":[{"url":"https://git.kernel.org/stable/c/2d9fd0f01550aab4a0a1984b4379e50545906248","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/8242a8d9d7194d5ef8a8b38a5621ca0966a3ec15","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/a65ccabde6deb95baf9442bd98299e2248884162","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}],"tags":["nvd","cve.org"],"ingestedAt":"2026-09-24T16:47:15.891Z","slug":"CVE-2026-93823","body":"## Overview\n\nIn 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)\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}