CVE-2026-23163
Medium · 5.5CVSS
5.5
EPSS
0.1%
Published
Feb 14, 2026
CISA due date
—
Cloudanix analysis
Certain AMD graphics chips inside laptops and small PCs can cause the whole computer to crash when the graphics driver tries to recover from memory errors.
- Exploitation
- Local Privilege
- Attacker needs
- Low Privilege
- Complexity
- Moderate
- Impact
- Denial Of Service
- Component
- OS kernel
- Class
- Memory Corruption
- Remediation
- Patch
- Effort
- Low
- Patch risk
- Low
What it actually does
Unconditional dereference of uninitialized ih1 ring buffer in amdgpu_gmc_filter_faults_remove leads to NULL pointer dereference and kernel panic when SVM retry fault handling is active on APUs that lack secondary IH rings.
Why it matters to the business
Systems using affected AMD APUs experience unexpected kernel crashes and reboots when the default retry-fault setting is enabled, causing loss of availability and potential data loss for workloads running on those GPUs.
How an attack unfolds
An attacker with local user privileges crafts memory access patterns that trigger SVM page-fault recovery on an affected APU while noretry=0; the recovery path calls amdgpu_gmc_filter_faults_remove which passes an uninitialized ih1 structure to amdgpu_ih_decode_iv_ts_helper, resulting in a kernel NULL dereference crash.
How to fix it
Apply the upstream fix present in commit c74e2dbb5316898fb2113a8ea3a93b27698dbf68 or later; rebuild and boot a kernel containing the added ih1.ring_size guard and restored soft_ih support; alternatively set the noretry=1 module parameter on affected APUs until the kernel is updated.
How to confirm the fix worked
Confirm presence of the ring_size check inside amdgpu_gmc_filter_faults_remove and absence of the crash call trace after applying the patch; verify the running kernel commit or package version matches or supersedes c74e2dbb5316898fb2113a8ea3a93b27698dbf68.
Typical attack path
- Obtain local shell on target system
- Ensure noretry=0 is active (default on Renoir after the referenced change)
- Trigger GPU SVM page faults via userspace GPU or compute workload
- Force invocation of svm_range_restore_pages and subsequent fault filtering
- Trigger kernel panic via NULL pointer access
How to detect it
Search kernel logs and dmesg for the exact BUG line 'kernel NULL pointer dereference' together with the call trace containing amdgpu_ih_decode_iv_ts_helper, amdgpu_gmc_filter_faults_remove, svm_range_restore_pages, and gmc_v9_0_process_interrupt.
- BUG: kernel NULL pointer dereference, address: 0000000000000004
- RIP: 0010:amdgpu_ih_decode_iv_ts_helper+0x22/0x40 [amdgpu]
- amdgpu_gmc_filter_faults_remove+0x60/0x130 [amdgpu]
- svm_range_restore_pages+0xae5/0x11c0 [amdgpu]
- gmc_v9_0_process_interrupt+0x191/0x220 [amdgpu]
What your security team should do
- Patch to a kernel containing commit c74e2dbb5316898fb2113a8ea3a93b27698dbf68 within the next maintenance window
- Temporarily apply noretry=1 on Raven/Renoir systems if immediate reboot is not feasible
- Add kernel oops monitoring for the specific amdgpu_ih_decode_iv_ts_helper signature
- Review GPU driver deployment pipelines to ensure future stable kernels are adopted promptly
The record
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix NULL pointer dereference in amdgpu_gmc_filter_faults_remove On APUs such as Raven and Renoir (GC 9.1.0, 9.2.2, 9.3.0), the ih1 and ih2 interrupt ring buffers are not initialized. This is by design, as these secondary IH rings are only available on discrete GPUs. See vega10_ih_sw_init() which explicitly skips ih1/ih2 initialization when AMD_IS_APU is set. However, amdgpu_gmc_filter_faults_remove() unconditionally uses ih1 to get the timestamp of the last interrupt entry. When retry faults are enabled on APUs (noretry=0), this function is called from the SVM page fault recovery path, resulting in a NULL pointer dereference when amdgpu_ih_decode_iv_ts_helper() attempts to access ih->ring[]. The crash manifests as: BUG: kernel NULL pointer dereference, address: 0000000000000004 RIP: 0010:amdgpu_ih_decode_iv_ts_helper+0x22/0x40 [amdgpu] Call Trace: amdgpu_gmc_filter_faults_remove+0x60/0x130 [amdgpu] svm_range_restore_pages+0xae5/0x11c0 [amdgpu] amdgpu_vm_handle_fault+0xc8/0x340 [amdgpu] gmc_v9_0_process_interrupt+0x191/0x220 [amdgpu] amdgpu_irq_dispatch+0xed/0x2c0 [amdgpu] amdgpu_ih_process+0x84/0x100 [amdgpu] This issue was exposed by commit 1446226d32a4 ("drm/amdgpu: Remove GC HW IP 9.3.0 from noretry=1") which changed the default for Renoir APU from noretry=1 to noretry=0, enabling retry fault handling and thus exercising the buggy code path. Fix this by adding a check for ih1.ring_size before attempting to use it. Also restore the soft_ih support from commit dd299441654f ("drm/amdgpu: Rework retry fault removal"). This is needed if the hardware doesn't support secondary HW IH rings. v2: additional updates (Alex) (cherry picked from commit 6ce8d536c80aa1f059e82184f0d1994436b1d526)
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Linux | Kernel | 6.4.0 | 6.6.123 |
| openSUSE:Leap 16.0 | dtb-aarch64 | 0 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-64kb | 0 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-azure | 0 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-default | 0 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-default-base | 0 | 6.12.0-160000.27.1.160000.2.8 |
| openSUSE:Leap 16.0 | kernel-docs | 0 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-kvmsmall | 0 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-obs-build | 0 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-obs-qa | 0 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-rt | 0 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-source | 0 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-syms | 0 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-zfcpdump | 0 | 6.12.0-160000.27.1 |
Related vulnerabilities
- CVE-2026-23226 In the Linux kernel, the following vulnerability has been resolved: ksmbd: add chann_lock… Also affects Kernel
- CVE-2026-23225 In the Linux kernel, the following vulnerability has been resolved: sched/mmcid: Don't… Also affects Kernel
- CVE-2026-23230 In the Linux kernel, the following vulnerability has been resolved: smb: client: split… Also affects Kernel
- CVE-2026-23224 In the Linux kernel, the following vulnerability has been resolved: erofs: fix UAF issue… Also affects Kernel
- CVE-2026-23227 In the Linux kernel, the following vulnerability has been resolved: drm/exynos: vidi: use… Also affects Kernel
- CVE-2026-23223 In the Linux kernel, the following vulnerability has been resolved: xfs: fix UAF in… Also affects Kernel
- CVE-2026-23228 In the Linux kernel, the following vulnerability has been resolved: smb: server: fix leak… Also affects Kernel
- CVE-2026-23229 In the Linux kernel, the following vulnerability has been resolved: crypto: virtio - Add… Also affects Kernel