CVE-2026-97424

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amdgpu/ras: add ras_suspend callback and use it for cp_ecc_error_irq<br /> <br /> cp_ecc_error_irq is acquired in amdgpu_gfx_ras_late_init() but<br /> released in gfx_v9_0_hw_fini(), so the put site has to query<br /> amdgpu_irq_enabled() because the get is skipped on SR-IOV VF.<br /> <br /> ras_late_init / ras_fini have no suspend counterpart, so move the<br /> put to amdgpu_gfx_ras_suspend() / amdgpu_gfx_ras_fini() and add a<br /> matching ras_suspend callback that is invoked from<br /> amdgpu_ras_suspend() before disable_all_features(). The get and<br /> put now sit in the same place and check the same condition (not<br /> VF, funcs registered), no refcount querying needed.<br /> <br /> An active flag gates ras_fini so the<br /> suspend-then-unload-without-resume path falls into<br /> amdgpu_ras_block_late_fini_default() instead of double-releasing<br /> what ras_suspend already cleaned up.<br /> <br /> Drop the cp_ecc_error_irq put from gfx_v9_0_hw_fini(). gfx_v8_0<br /> manages cp_ecc_error_irq locally and is unaffected; no other GFX<br /> generation has this IRQ.