Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.newCreate a CVE report
Check your stack
CVE-2026-93823

drm/amdkfd: Let driver decide buffer size at AMDKFD_IOC_GET_DMABUF_INFO ioctl

Products / packages Linux

Published

Share

Severity and exploitation

Not in CISA KEVNo CVSS score

KEV coverage does not rule out exploitation.

KEV checked 14/11/2026, 22:55:31 UTC

Severity

unknown

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Not established by this record

Missing evidence does not mean no public exploit exists.

Remediation

Fix status not established

No structured fix or guidance is available here. Check the latest publisher advisory.

What this means

In the Linux kernel, the following vulnerability has been resolved:

Source excerpt · Linux

Attack conditions

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

Linux · Linux

Linux

5 ranges
Linux version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

1dde0ea95b782425b95455d487cb44991525a1d1 → before d298c100796b2cd1e7e75f8e615b79d034e510f8

git versions

1dde0ea95b782425b95455d487cb44991525a1d1 → before d51841bb5ceee75ec3aeeb4e5c51c8e5e7524228

git versions

1dde0ea95b782425b95455d487cb44991525a1d1 → before a65ccabde6deb95baf9442bd98299e2248884162

git versions

1dde0ea95b782425b95455d487cb44991525a1d1 → before 2d9fd0f01550aab4a0a1984b4379e50545906248

git versions

1dde0ea95b782425b95455d487cb44991525a1d1 → before 8242a8d9d7194d5ef8a8b38a5621ca0966a3ec15

git versions

unaffected

unknown

Other versions: unaffected

Linux · Linux

Linux

7 ranges
Linux version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

5.0

unaffected

0 → before 5.0

semver versions

6.1.191 → through 6.1.*

semver versions

6.6.158 → through 6.6.*

semver versions

6.12.111 → through 6.12.*

semver versions

6.18.53 → through 6.18.*

semver versions

7.2 → through *

original_commit_for_fix versions

unknown

Other versions: affected

Automatic dependency matching is unavailable for this record. Use the product evidence and publisher’s instructions to check your installation.

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

No structured fix or remediation guidance is available here. Check the full source description and vendor’s latest advisory for a patch or workaround; do not assume another version is safe.

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.

Original source description

Read the full publisher 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)

References

5 sources
git.kernel.org/stable/c/d298c100796b2cd1e7e75f8e615b79d034e510f8
Source referenceLinux
git.kernel.org/stable/c/d51841bb5ceee75ec3aeeb4e5c51c8e5e7524228
Source referenceLinux
git.kernel.org/stable/c/a65ccabde6deb95baf9442bd98299e2248884162
Source referenceLinux
git.kernel.org/stable/c/2d9fd0f01550aab4a0a1984b4379e50545906248
Source referenceLinux
git.kernel.org/stable/c/8242a8d9d7194d5ef8a8b38a5621ca0966a3ec15
Source referenceLinux

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance · not supplied
Weakness classification · not supplied
Additional publishers · not supplied

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-93823

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Environment requirements

These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.

Linux · platform conditions

Any condition may hold

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 5.0

Before: 6.1.191

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 5.0

Before: 6.6.158

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 5.0

Before: 6.12.111

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 5.0

Before: 6.18.53

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 5.0

Before: 7.2

Applicability preview
[
  {
    "nodes": [
      {
        "operator": "OR",
        "negate": false,
        "cpeMatch": [
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "5.0",
            "versionEndExcluding": "6.1.191"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "5.0",
            "versionEndExcluding": "6.6.158"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "5.0",
            "versionEndExcluding": "6.12.111"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "5.0",
            "versionEndExcluding": "6.18.53"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "5.0",
            "versionEndExcluding": "7.2"
          }
        ]
      }
    ]
  }
]
Contributing organizations · 1
Linux

Assigning organization

2026-10-30

Timeline

All times UTC

  1. Advisory published

    Publication date supplied by the source.

  2. Source updated

    Latest modification date supplied by the source.

  3. Last imported by cve.new

    Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.