VulnerabilityPublished 18 Oct 2026Updated 26 Oct 2026

CVE-2026-98784: Linux kernel · drm/amdgpu/gfx6: fix firmware leak on teardown

Affects Linux kernelSource CVE Database V5

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

Data as of 26 Oct 2026, 14:18 UTC

Severity

Low

Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in cc172e177795c5f87bc2d71768d077e1c10633e8, 652f631e2e3a8d3b11ad72dd0b8e59b5183de0d9, 4b70c6b34912ca0b4066f56fd627d785dfbfe1fa +2

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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 to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 2cd46ad22383ab8372b86cdb5257589496099412, < cc172e177795c5f87bc2d71768d077e1c10633e8	Fixed in cc172e177795c5f87bc2d71768d077e1c10633e8
LinuxLinux	Affected ≥ 2cd46ad22383ab8372b86cdb5257589496099412, < 652f631e2e3a8d3b11ad72dd0b8e59b5183de0d9	Fixed in 652f631e2e3a8d3b11ad72dd0b8e59b5183de0d9
LinuxLinux	Affected ≥ 2cd46ad22383ab8372b86cdb5257589496099412, < 4b70c6b34912ca0b4066f56fd627d785dfbfe1fa	Fixed in 4b70c6b34912ca0b4066f56fd627d785dfbfe1fa
LinuxLinux	Affected ≥ 2cd46ad22383ab8372b86cdb5257589496099412, < 3a86ebf6aa8b0a845e6188daaa6f530fe67ff00e	Fixed in 3a86ebf6aa8b0a845e6188daaa6f530fe67ff00e
LinuxLinux	Affected ≥ 2cd46ad22383ab8372b86cdb5257589496099412, < 2aee72150b0ea92804f0f2799efb129f10e46e8d	Fixed in 2aee72150b0ea92804f0f2799efb129f10e46e8d
LinuxLinux	Affected =4.9	Fixed in–

AI-suggested

A fix is available and has been applied in multiple commits and versions of the Linux kernel. Users and administrators should update to a fixed kernel version that includes the patch identified by the commits (e.g., cc172e177795c5f87bc2d71768d077e1c10633e8 and others).

Description

A vulnerability in the Linux kernel's AMDGPU driver (gfx6) caused firmware resources to leak during teardown because the firmware requested in gfx_v6_0_init_microcode() was not properly released. This issue has been fixed by adding a function to free the microcode firmware during the software finalization phase.

Impact

The vulnerability causes a resource leak of firmware components during the teardown of the AMDGPU gfx6 block in the Linux kernel. While this does not directly indicate a security compromise such as code execution or privilege escalation, leaking firmware resources can lead to increased memory usage and potential system instability over time.

Summary

The Linux kernel AMDGPU gfx6 driver did not release firmware resources when tearing down the GFX block, leading to a firmware leak. Specifically, the firmware requested in gfx_v6_0_init_microcode() was not freed. The fix involved adding gfx_v6_0_free_microcode() and calling it from gfx_v6_0_sw_fini() to release the PFP, ME, CE, and RLC firmware components. This fix was applied in several commits and versions.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Oct 2026, 09:31 UTC

Technical details

References

Community reviews

Related threats