CVE-2026-93823 Linux CVE debrief

Who should care

Linux kernel developers and administrators responsible for maintaining systems with the vulnerable component should assess exposure and apply patches or updates. They should verify buffer size handling in kernel components, assess exposure to potential OOM conditions, and monitor system logs for OOM conditions. This includes reviewing compensating controls for exposed systems and tracking exceptions and retesting remediated assets.

Why it matters

A vulnerability in the Linux kernel's drm/amdkfd component could lead to a potential out-of-memory (OOM) condition. Linux kernel developers and administrators should assess exposure and apply patches or updates.

• Verify buffer size handling in kernel components
• Assess exposure to potential OOM conditions
• Monitor system logs for OOM conditions

Technical summary

The Linux kernel's drm/amdkfd component is vulnerable to a potential out-of-memory (OOM) condition. A user can trigger this by providing a hostile buffer size value to the AMDKFD_IOC_GET_DMABUF_INFO ioctl, allowing for an order-MAX allocation in kernel context. The issue is resolved by having the driver decide the buffer allocation size. This change lets the driver allocate buffer to return bo metadata to user space safely. The buffer size is controlled by the driver, not the user, to avoid potential hostile size from user space.

Defensive priority

Assess exposure and apply patches

Recommended defensive actions

• Assess exposure to the vulnerable component
• Apply patches or updates provided by the vendor
• Monitor system logs for potential OOM conditions
• Verify buffer size handling in kernel components
• Review compensating controls for exposed systems
• Track exceptions and retest remediated assets
• Check relevant monitoring, detection, and logs for exposed assets

Evidence notes

The CVE record and NVD entry provide details on the vulnerability. Three source references are provided, detailing the specific commits that resolve the issue. The vulnerability allows a user to trigger a potential out-of-memory (OOM) condition by providing a hostile buffer size value to the AMDKFD_IOC_GET_DMABUF_INFO ioctl. Linux kernel developers and administrators should verify buffer size handling in kernel components, assess exposure to potential OOM conditions, and monitor system logs for OOM conditions. Evidence limits suggest

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.