[CVE-2026-74353][LOW] drm/amdkfd: always resume_all after suspend_all [ Upstream

[CVE-2026-74353][LOW] drm/amdkfd: always resume_all after suspend_all [ Upstream

[AL-KERNEL]

CVE: CVE-2026-74353
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: drm/amdkfd: always resume_all after suspend_all [ Upstream
Commit: e29da2a4d9a3b1837dec3ce0892835d506c2a85e
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e29da2a4d9a3b1837dec3ce0892835d506c2a85e
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74353
Analysis date: Sun, 16 Aug 2026 02:20:31 -0400
ActionableScore: 2
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
No one-sentence report phrase was found.

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

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

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-74353	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-703;CWE-755;CWE-404;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.5';DESCR 'AMD KFD bad queue handling can leave good GPU queues suspended when suspend_all_queues_mes fails before the recovery path completes. A local process with access to AMD KFD or render GPU devices may be able to trigger this through a bad GPU queue condition, causing denial of service for GPU workloads or requiring GPU reset based recovery. For the CVSS the PR:L is used because a local user or service account with GPU queue access is sufficient in many compute deployments, while administrator privileges are not necessarily required after device access is granted. The issue is not network reachable and does not affect packet or remote protocol processing. Impact is denial of service only. There is no concrete evidence of UAF, OOB access, information disclosure, arbitrary write, or privilege escalation in the shown code path.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 2)  SKIP CVE-2026-74353 UNKNOWN SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	SIMPLEFIX ERRORPATH HARDWARE  INCREASED_FROM_LOW_BASED_ON_HIGHCVSSSCORE DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5 DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	-	-	checked

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

ActionableScore=2

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

2. Signal breakdown
* Local unprivileged trigger: +1. A local process with access to AMD KFD or render GPU devices may be able to create or trigger the bad queue condition.
* Reliable device-level DoS concern: +1. The bug can leave good GPU queues suspended or require GPU reset based recovery, affecting GPU workloads.
* No memory corruption signal: +0. The patch shows error path and recovery ordering fixes only. There is no UAF, OOB access, double free, arbitrary write, refcount misuse, or type confusion.
* No privilege escalation signal: +0. The affected path does not expose a demonstrated LPE primitive.
* No network reachability: +0. This is not reachable through packet processing or a remote protocol.
* No broad default exposure bonus: +0. Exposure depends on AMD GPU KFD or MES queue usage and local device access.

3. Reachability analysis
The realistic trigger is local and requires access to AMD KFD or render GPU device nodes. In many GPU compute deployments this may be available to non-root users or service accounts through device permissions, so PR:L is reasonable for CVSS-style reasoning. Namespaces or containers matter only if the GPU device is passed through or exposed to the container. The path is not network reachable and is not a default core kernel path on systems without affected AMD GPU KFD usage.

4. Severity interpretation
This behaves like an ordinary Moderate or Low-like device DoS issue rather than an Important kernel vulnerability. The realistic impact is disruption of GPU queues, failed recovery, or GPU reset requirements. Theoretical escalation is not supported by the shown patch because the bug is an error-handling and recovery-ordering issue, not a memory lifetime or corruption primitive.

5. One-sentence report phrase
AMD KFD bad queue recovery could fail to resume good queues after suspend_all_queues_mes failure, allowing a local GPU user to cause GPU workload denial of service without evidence of memory corruption or privilege escalation.

6. Manual review recommendation
NO MANUAL CHECK NEEDED. The patch supports DoS-only GPU queue recovery impact, with no concrete memory corruption, security boundary bypass, remote exposure, or privilege escalation path.

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

Patch: drm/amdkfd: always resume_all after suspend_all [ Upstream
Commit: e29da2a4d9a3b1837dec3ce0892835d506c2a85e
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e29da2a4d9a3b1837dec3ce0892835d506c2a85e

Changed files:
  drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.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=e29da2a4d9a3b1837dec3ce0892835d506c2a85e

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

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

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:L
  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: unknown
  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).