Description
In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu: Skip KFD mapping clear before initialization

amdgpu_amdkfd_clear_kfd_mapping() assumes that a non-NULL kfd_dev
has a fully populated node array. This is not true when KFD device
initialization fails after probe.

For example, kgd2kfd_device_init() sets num_nodes before checking
PCIe atomics support. On Polaris systems without the required atomics,
it returns before allocating nodes[0], but the kfd_dev remains attached
to the amdgpu device. A later GPU reset then dereferences nodes[0]->id.

Require the authoritative KFD initialization flag before walking the
node array, matching the existing KFD reset and teardown paths.

(cherry picked from commit 4ac1835823c47903fbb278bbf474773c46f59edc)
Published: 2026-10-06
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Denial of Service via kernel crash
Action: Patch immediately
AI Analysis

Impact

The vulnerability arises when the AMDGPU KFD driver assumes a fully populated node array during initialization. If initialization fails before allocating nodes, the kernel later dereferences a null or uninitialized node during a GPU reset, causing a kernel crash. The result is a denial of service on a system with privileged kernel access. Based on the description, it does not provide remote code execution capabilities.

Affected Systems

Affected systems are Linux kernel installations that include the AMDGPU driver where the KFD runtime may be enabled. The vulnerability is present in kernel code that has not yet applied the commit that checks the KFD initialization flag before accessing the node array. No specific kernel version ranges are provided in the CVE data.

Risk and Exploitability

The EPSS score of < 1% indicates a very low probability of exploitation, and the vulnerability is not listed in the CISA KEV catalog. Based on publicly available information, no exploit has been reported; however, this conclusion is inferred from the absence of documented exploits. A local or privileged attacker could still trigger a kernel crash by causing a GPU reset after a failed KFD initialization. The risk level is moderate, as it requires kernel-level access or a device that can provoke a reset on a compromised or misconfigured system. The CVSS score is 5.5, reflecting a medium severity vulnerability.

Generated by OpenCVE AI on October 9, 2026 at 05:37 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply an updated Linux kernel that includes the fix for the KFD mapping clear before initialization (commit 4ac1835823c47903fbb278bbf474773c46f59edc).
  • Ensure the AMDGPU driver is initialized only after verifying PCIe atomics support on Polaris or equivalent hardware, or disable KFD if atomics are missing.
  • Reboot the system after applying the update to clear any residual corrupted kernel state.

Generated by OpenCVE AI on October 9, 2026 at 05:37 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 09 Oct 2026 04:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-665

Fri, 09 Oct 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-476
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Low


Wed, 07 Oct 2026 07:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-665

Wed, 07 Oct 2026 05:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-476

Tue, 06 Oct 2026 12:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-476

Tue, 06 Oct 2026 09:00:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Skip KFD mapping clear before initialization amdgpu_amdkfd_clear_kfd_mapping() assumes that a non-NULL kfd_dev has a fully populated node array. This is not true when KFD device initialization fails after probe. For example, kgd2kfd_device_init() sets num_nodes before checking PCIe atomics support. On Polaris systems without the required atomics, it returns before allocating nodes[0], but the kfd_dev remains attached to the amdgpu device. A later GPU reset then dereferences nodes[0]->id. Require the authoritative KFD initialization flag before walking the node array, matching the existing KFD reset and teardown paths. (cherry picked from commit 4ac1835823c47903fbb278bbf474773c46f59edc)
Title drm/amdgpu: Skip KFD mapping clear before initialization
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-19T09:15:09.614Z

Reserved: 2026-09-25T10:25:14.322Z

Link: CVE-2026-98178

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-06T09:17:59.930

Modified: 2026-10-19T10:18:18.153

Link: CVE-2026-98178

cve-icon Redhat

Severity : Low

Publid Date: 2026-10-06T00:00:00Z

Links: CVE-2026-98178 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-09T05:45:20Z

Weaknesses