[CVE-2026-97424][LOW] drm/amdgpu/ras: add ras_suspend callback and use it for cp_ecc_error_irq [ Upstream

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

CVE: CVE-2026-97424
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: drm/amdgpu/ras: add ras_suspend callback and use it for cp_ecc_error_irq [ Upstream
Commit: 001824103f2fe6ffd2380afddf81f43b446035b2
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=001824103f2fe6ffd2380afddf81f43b446035b2
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-97424
Analysis date: Thu, 24 Sep 2026 20:15:20 -0400
ActionableScore: 0
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
No one-sentence report phrase was found.

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

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

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-97424	LOW	https://www.kernelcve.org/list/?q=CVE-2026-97424 CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';CWE-675;CWE-404;*CWE-664;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.7';DESCR 'The AMDGPU GFX RAS path acquires cp_ecc_error_irq during late initialization but previously released it from a different hardware shutdown path. A suspend followed by driver unload without resume can therefore release the same IRQ reference again, while SR-IOV VF configurations can also reach cleanup without the corresponding acquisition. The likely effects are an IRQ reference count imbalance, warning, incorrect interrupt state, failed GPU recovery, or loss of GPU availability. No stale memory dereference, out of bounds access, information disclosure, or arbitrary write primitive is demonstrated by the affected paths. For the CVSS the PR:L value is used for the paranoid score because suspend or GPU lifecycle operations may be delegated to a local service, reduced capability administrator, container root, or desktop power management user in some deployments. The issue is not network reachable. Impact is limited to availability and the supplied code does not support privilege escalation or confidentiality and integrity impact.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 0)  SKIP CVE-2026-97424 UNKNOWN SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	INIT ERRORPATH HARDWARE 	-	-	checked

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

ActionableScore=0
PrimitiveClass=CLASS_C
RealUAF=NO
HostAdminRequired=YES
NamespaceScopedPrivilege=NO
ImportantCandidate=NO
ManualReview=NO
AutoDowngradeAllowed=YES

1. ActionableScore

* Raw conservative score: -1.
* Conservative score: 0. The raw result was clamped to the minimum ActionableScore of 0.
* Raw paranoid score: -1.
* Paranoid score: 0. The raw result was clamped to the minimum ActionableScore of 0.
* Final recommended bucket: **Ordinary Moderate**::

2. Signal breakdown

* +1 Availability impact realistic. A duplicate `amdgpu_irq_put()` can corrupt the IRQ enable-reference state, cause warnings, prevent correct interrupt restoration, or leave the GPU unavailable until driver or system recovery.
* -2 Proven host-administrator-equivalent trigger. The concrete problematic sequence requires RAS suspend followed by driver unload or device teardown without resume. Unloading or unbinding the host AMDGPU driver requires host administrative control.
* +0 Real UAF not awarded. `cp_ecc_error_irq` is embedded AMDGPU IRQ state, and the supplied code does not show that `amdgpu_irq_put()` frees this object or ends its memory lifetime.
* +0 Concrete repeated release/refcount signal not awarded. Two puts can occur for the same IRQ acquisition, but this is an IRQ enable/accounting reference rather than an established object-lifetime reference whose first put can destroy or free the referenced object.
* +0 Reliable kernel crash not awarded. The supplied evidence supports an IRQ-state imbalance and possible GPU failure, but not a host kernel panic or fatal stale-pointer dereference.
* +0 Strong or weak exploitation leverage not awarded. No controlled reclaim, arbitrary write, callback influence, stale structured-object consumption, disclosure, or privilege-escalation mechanism is established.
* +0 Extra availability not awarded. No persistent host-wide effect distinct from the possible GPU disruption is shown.
* +0 Remote reachability not awarded. No packet, device input, or network-accessible interface reaches this lifecycle sequence.
* +0 Paranoid escalation withheld. The second put does not establish post-free lifetime metadata mutation, so the repeated-refcount paranoid rule does not apply.
* FLOOR 5 was not applied because there is no real UAF and no second operation on a potentially freed object.

3. Reachability analysis

The concrete sequence is suspend followed by AMDGPU driver unload, unbind, or equivalent teardown without an intervening resume. System suspend may be requested through a desktop power-management service, but that alone does not give an ordinary logged-in user control over the required driver unload or device teardown stage.

A DRM master, compositor, display server, or ordinary render-node user is not shown to control the complete sequence. The complete demonstrated trigger instead requires host-level driver or device lifecycle management. No namespace-scoped capability path is involved, and a container-local capability does not ordinarily permit unloading or unbinding the host GPU driver.

The affected path additionally requires AMDGPU GFX RAS support and the relevant `cp_ecc_error_irq`, apparently on affected GFX generation 9 hardware. AMD GPU hardware itself is not treated as rare, and no hardware rarity penalty is applied. This is an ordered lifecycle sequence, not a timing race, so no race-complexity penalty is applied.

4. Primitive and severity interpretation

The exact primitive is duplicate decrement or release of an IRQ enable reference after suspend cleanup, together with inconsistent acquisition and release conditions for SR-IOV VF handling. It is a resource-state and accounting defect rather than demonstrated memory-lifetime corruption.

This differs from a true repeated-lifetime UAF:

* The first `amdgpu_irq_put()` can disable the IRQ and reduce its enable count, but the evidence does not show that it frees `cp_ecc_error_irq`.
* The same embedded IRQ source remains addressable because its containing AMDGPU device object is still present during teardown.
* The later put mutates IRQ accounting, but not demonstrated freed object storage.
* Therefore, this is not category B second lifetime mutation through a dangling object.

The issue is classified as CLASS_C because its supported consequences are invalid IRQ state, warnings, failed recovery, or device-local availability loss. A host crash or privilege escalation is speculative and unsupported. There is no useful primitive remaining after excluding the accounting failure and possible GPU disruption.

ImportantCandidate is NO because neither memory corruption nor a security-boundary primitive is established. AutoDowngradeAllowed is YES because the complete trigger requires host administrative lifecycle control and no unresolved post-lifetime corruption mechanism remains. Operational severity is Low-like or ordinary Moderate, primarily affecting GPU reliability during an unusual suspend-and-unload sequence.

5. One-sentence report phrase

An inconsistent AMDGPU RAS IRQ lifecycle could double-release the cp_ecc_error_irq enable reference during suspend followed by driver teardown, potentially causing IRQ-state corruption and GPU availability problems but not a demonstrated memory-safety or privilege-escalation issue.

6. Manual review recommendation

NO MANUAL CHECK NEEDED

The patch establishes a host-admin-controlled IRQ accounting and cleanup defect without a real UAF, host-wide crash, disclosure, arbitrary write, or security-boundary bypass.

7. Call-site confidence

Call-site confidence: high

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

Patch: drm/amdgpu/ras: add ras_suspend callback and use it for cp_ecc_error_irq [ Upstream
Commit: 001824103f2fe6ffd2380afddf81f43b446035b2
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=001824103f2fe6ffd2380afddf81f43b446035b2

Changed files:
  drivers/gpu/drm/amd/amdgpu/amdgpu_gfx.c
  drivers/gpu/drm/amd/amdgpu/amdgpu_gfx.h
  drivers/gpu/drm/amd/amdgpu/amdgpu_ras.c
  drivers/gpu/drm/amd/amdgpu/amdgpu_ras.h
  drivers/gpu/drm/amd/amdgpu/gfx_v9_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=001824103f2fe6ffd2380afddf81f43b446035b2

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

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

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:H/UI:N/S:U/C:N/I:N/A:L
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.7

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: 0

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).