CVE-2026-68252

Received Received - Intake

AMDGPU SDMA7.0 BUG_ON Replacement in Linux Kernel

Publication date: 2026-08-10

Last updated on: 2026-08-18

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/sdma7.0: replace BUG_ON() with WARN_ON() There's no need to crash the kernel for these cases. (cherry picked from commit 9723a8bed3aa251a26bee4583bac9d8fb064dd44)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-10

Last Modified

2026-08-18

Generated

2026-08-31

AI Q&A

2026-08-10

EPSS Evaluated

2026-08-29

NVD

CVE-2026-68252

EUVD

EUVD-2026-55353

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability involves a flaw in the Linux kernel's AMD GPU driver for SDMA 7.0. Instead of crashing the kernel with BUG_ON(), the code now uses WARN_ON() to handle error cases, preventing system crashes.

Detection Guidance

This vulnerability is specific to the Linux kernel's AMDGPU SDMA7.0 driver and involves replacing a BUG_ON() with WARN_ON(). Detection requires checking kernel logs for WARN_ON() messages related to amdgpu or sdma7.0. Use commands like 'dmesg | grep -i amdgpu' or 'journalctl -k | grep -i sdma7.0' to inspect kernel logs for warnings.

Impact Analysis

This vulnerability could lead to system instability or crashes if the kernel encounters certain error conditions in the AMD GPU driver. Users may experience graphical issues or unexpected system reboots.

Compliance Impact

This vulnerability does not directly affect compliance with standards like GDPR or HIPAA as it relates to a kernel crash prevention in AMD GPU drivers and does not involve data handling or privacy concerns.

Mitigation Strategies

Apply the latest Linux kernel update to address the AMDGPU SDMA7.0 BUG_ON() issue. Monitor system logs for warnings related to AMDGPU after updating.

Hi! I’m here to help you understand CVE-2026-68252. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70