VulnerabilityPublished 14 Feb 2026Updated 5 Nov 2026

CVE-2026-23163: Linux kernel · drm/amdgpu: fix NULL pointer dereference in amdgpu_gmc_filter_faults_remove

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in c74e2dbb5316898fb2113a8ea3a93b27698dbf68 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 23:24 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

EPSS

0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch

Available – fixed in c74e2dbb5316898fb2113a8ea3a93b27698dbf68, ac251d17d8af58ddc3daba65eaf0a99e63dc4284, 7611d7faccc1218be477671f892a89b25c0cb352 +1

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to c74e2dbb5316898fb2113a8ea3a93b27698dbf68, ac251d17d8af58ddc3daba65eaf0a99e63dc4284, 7611d7faccc1218be477671f892a89b25c0cb352 or 8b1ecc9377bc641533cd9e76dfa3aee3cd04a007.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ dd299441654fd8209056c7985ddf2373ebaba6ed, < c74e2dbb5316898fb2113a8ea3a93b27698dbf68	Fixed in c74e2dbb5316898fb2113a8ea3a93b27698dbf68
LinuxLinux	Affected ≥ dd299441654fd8209056c7985ddf2373ebaba6ed, < ac251d17d8af58ddc3daba65eaf0a99e63dc4284	Fixed in ac251d17d8af58ddc3daba65eaf0a99e63dc4284
LinuxLinux	Affected ≥ dd299441654fd8209056c7985ddf2373ebaba6ed, < 7611d7faccc1218be477671f892a89b25c0cb352	Fixed in 7611d7faccc1218be477671f892a89b25c0cb352
LinuxLinux	Affected ≥ dd299441654fd8209056c7985ddf2373ebaba6ed, < 8b1ecc9377bc641533cd9e76dfa3aee3cd04a007	Fixed in 8b1ecc9377bc641533cd9e76dfa3aee3cd04a007
LinuxLinux	Affected =6.4	Fixed in–

Description

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)

References

Community reviews

Loading reviews…