LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23358: drm/amdgpu: Fix error handling in slot reset

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix error handling in slot reset If the device has not recovered after slot reset is called, it goes to out label for error handling. There it could make decision based on uninitialized hive pointer and could result in accessing an uninitialized list. Initialize the list and hive properly so that it handles the error situation and also releases the reset domain lock which is acquired during error_detected callback. (cherry picked from commit bb71362182e59caa227e4192da5a612b09349696)

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel AMDGPU driver flaw in error handling during PCI slot reset recovery. If a GPU does not recover, the kernel may make decisions using uninitialized reset-domain data. The public record does not provide a CVSS score, confirmed impact, or active exploitation evidence.

Executive priority

Track and patch through normal kernel maintenance, with higher urgency for business-critical systems relying on AMD GPUs. Current public evidence does not justify emergency treatment, but incomplete severity data means exposed fleets should not ignore it.

Technical view

The resolved bug is in drm/amdgpu slot reset handling. On an unrecovered device path, error handling could use an uninitialized hive pointer and list, and mishandle reset-domain lock release. Stable kernel commits initialize the list and hive properly before this path is reached.

Likely exposure

Exposure is most relevant to Linux systems using the AMDGPU kernel driver, especially hosts with AMD GPUs where device reset and recovery paths can occur. The source bundle lists Linux as affected for several version entries but does not clearly map distro package versions or all fixed releases.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of exploitation in the wild. The described condition depends on AMDGPU slot reset failure handling, but the sources do not establish attacker reachability, privilege requirements, or practical exploitability.

Researcher notes

Impact assessment is limited by missing CVSS, CWE, and distro mappings. Focus validation on whether the affected AMDGPU reset path exists in deployed kernels and whether vendor kernels include the stable fixes or equivalent backports.

Mitigation direction

  • Update to a vendor Linux kernel that includes the referenced stable fixes.
  • Check distribution advisories for backported fixes matching your kernel package.
  • Prioritize GPU compute, rendering, desktop, and virtualization hosts using AMDGPU.
  • Plan maintenance for systems where GPU reset instability would affect availability.
  • If no vendor fix is available, monitor kernel guidance and reduce exposure where feasible.

Validation and detection

  • Inventory Linux hosts with AMD GPUs or the AMDGPU driver loaded.
  • Map running kernel packages to vendor advisories or fixed stable commits.
  • Review kernel change logs for the referenced stable commit identifiers.
  • Check operational logs for recurring AMDGPU reset or PCI recovery failures.
  • Confirm patched systems rebooted into the updated kernel.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23358 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux732c6cefc1ecfc8de5d7a2029480798655d979d8, 732c6cefc1ecfc8de5d7a2029480798655d979d8, 732c6cefc1ecfc8de5d7a2029480798655d979d8unaffected
LinuxLinux6.16, 0, 6.18.17, 6.19.7, 7.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.