[CVE-2026-68115][LOW] drm/amdgpu/gfx10: replace BUG_ON() with WARN_ON()

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-68115
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: drm/amdgpu/gfx10: replace BUG_ON() with WARN_ON()
Commit: 793cdf17ddf9dc662a94cae86ce005565ef3c1c2
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=793cdf17ddf9dc662a94cae86ce005565ef3c1c2
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68115
Analysis date: Mon, 10 Aug 2026 19:21:21 -0400
ActionableScore: 2
ActionableScore lower bound: 1
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
amdgpu gfx10 used BUG_ON() assertions in GPU ring emission paths, so certain malformed or unexpected local GPU driver states could panic the kernel, but the patch does not indicate memory corruption, information disclosure, or privilege escalation.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-68115 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68115

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: LOW
Manual review required: NO

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-68115	LOW	CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H';CWE-617;CWE-754;CWE-703;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.5';DESCR 'amdgpu gfx10 uses BUG_ON() assertions in GPU ring emission paths for misaligned addresses and an unsupported 64 bit KIQ fence flag. If one of these internal invariants is reached, the old code panics the kernel, turning a malformed or unexpected GPU submission state into a local denial of service. For the CVSS the PR:L is used for the paranoid score because local access to a DRM render or card device may be enough in some deployments, even though reliable triggering depends on driver paths and device state. The issue is not network reachable and the impact is denial of service only. No evidence in the patch indicates a UAF, OOB access, information leak, or privilege escalation primitive.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 2)  SKIP CVE-2026-68115 UNKNOWN SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	OOB DANGER SIMPLEFIX KERNEL_PANIC_PLUS_UAF HARDWARE PACKET  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	-	-	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=2
ActionableScoreLower=1

## 1. ActionableScore

* Conservative score: 1
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate / Low-like**

## 2. Signal breakdown

Conservative signals:

* Reliable kernel crash / strong DoS: +1. The old code used BUG_ON() in amdgpu gfx10 ring emission paths, so reaching these alignment or flag conditions could panic the kernel.
* Hard or unreliable trigger / special condition: -1. The patch does not show a direct user-controlled parameter that reliably reaches these BUG_ON() sites. Triggering likely depends on specific GPU submission paths, driver state, or malformed internal state.
* Availability impact realistic: +1. A reached BUG_ON() is a host kernel panic, but this mostly duplicates the strong DoS signal, so I would not double-count it in the conservative score unless the trigger is proven reliable.

Conservative total after avoiding double-counted availability: 1.

Paranoid signals:

* Local unprivileged trigger: +1. In some deployments, local users can access DRM render or card device nodes and may influence GPU command submission paths.
* Reliable kernel crash / strong DoS: +1. BUG_ON() is an unconditional kernel crash if the invariant is reached.
* No memory corruption bonus. The patch does not show UAF, OOB write, double free, stale pointer reuse, type confusion, refcount abuse, or attacker-controlled overwrite.
* No LPE bonus. There is no plausible privilege escalation primitive in the diff or commit message.
* No network reachability. This is local GPU driver behavior, not a packet or remote protocol path.

Paranoid total: 2.

## 3. Reachability analysis

The likely trigger is local access to amdgpu DRM paths on systems with affected gfx10 hardware. A normal unprivileged desktop user may have access to DRM render nodes, but the patch does not prove that user input can directly create the misaligned gpu_addr, misaligned fence address, or unsupported KIQ fence flag state. Containers usually do not get GPU device access unless explicitly passed through, so container reachability depends on device delegation. The path is not network reachable. The affected subsystem is common on AMD GPU systems, but the specific gfx10 hardware and invariant-triggering conditions make exploitation configuration-dependent.

Call-site confidence: medium. The changed functions are visible and are ring emission helpers, but the exact user-to-helper path and controllability of the bad alignment or flag values are not shown in the supplied patch.

## 4. Severity interpretation

This behaves like an ordinary Moderate or Low-like local DoS issue. The concrete impact is kernel panic caused by reachable BUG_ON() assertions. Theoretical follow-on impact is weak because the patch only changes assertions to warnings or removes an unnecessary assertion. It does not fix a demonstrated memory lifetime issue, bounds violation, ownership bypass, or corruption primitive. Therefore it should not be treated as an Important-class kernel vulnerability based on the supplied evidence.

## 5. One-sentence report phrase

amdgpu gfx10 used BUG_ON() assertions in GPU ring emission paths, so certain malformed or unexpected local GPU driver states could panic the kernel, but the patch does not indicate memory corruption, information disclosure, or privilege escalation.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

This can be auto-closed or handled as ordinary Moderate unless additional external evidence shows a reliable unprivileged trigger or a downstream memory corruption primitive beyond the BUG_ON() crash.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: drm/amdgpu/gfx10: replace BUG_ON() with WARN_ON()
Commit: 793cdf17ddf9dc662a94cae86ce005565ef3c1c2
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=793cdf17ddf9dc662a94cae86ce005565ef3c1c2

Commit description:

There's no need to crash the kernel for these cases.

Reviewed-by: Vitaly Prosyak <vitaly.prosyak@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
(cherry picked from commit ac6f00b )
Cc: stable@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=793cdf17ddf9dc662a94cae86ce005565ef3c1c2

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-68115 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68115

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 5.5

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 1
  Paranoid ActionableScore: 2

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).