Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-93823drm/amdkfd: Let driver decide buffer size at AMDKFD_IOC_GET_DMABUF_INFO ioctl

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Let driver decide buffer size at AMDKFD_IOC_GET_DMABUF_INFO ioctl amdkfd driver needs allocate buffer to return bo metadata to user space. The buffer size is controlled by user currently. It is a potential security issue that hostile value (e.g. 2 GiB) lets any render-group user trigger order-MAX allocation/OOM in kernel context. This patch first finds bo metadata size. If the size is smaller than user provided value drive can safely allocate buffer in kernel space and copy to user space buffer. If not, driver will let user know, not allocate and copy. User will redo with new buffer in user space. This patch lets driver decide buffer allocation size to avoid potential hostile size from user space. (cherry picked from commit f54ce9e8cbd3abe0eda3a285f54dc4f572fe589a)

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 36 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 1dde0ea95b782425b95455d487cb44991525a1d1 – < d298c100796b2cd1e7e75f8e615b79d034e510f8
    • affected 1dde0ea95b782425b95455d487cb44991525a1d1 – < d51841bb5ceee75ec3aeeb4e5c51c8e5e7524228
    • affected 1dde0ea95b782425b95455d487cb44991525a1d1 – < a65ccabde6deb95baf9442bd98299e2248884162
    • affected 1dde0ea95b782425b95455d487cb44991525a1d1 – < 2d9fd0f01550aab4a0a1984b4379e50545906248
    • affected 1dde0ea95b782425b95455d487cb44991525a1d1 – < 8242a8d9d7194d5ef8a8b38a5621ca0966a3ec15
  • Linux · Linux

    • affected 5.0
    • unaffected < 5.0
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93823 badge
[![CVE-2026-93823](https://cveledger.app/badge/CVE-2026-93823.svg)](https://cveledger.app/cve/CVE-2026-93823)

Record last updated .