CVE-2026-97519: drm/xe: Fix null pointer dereference in devcoredump cleanup
drm/xe: Fix null pointer dereference in devcoredump cleanup
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1
Event History
Frequently Asked Questions
What condition triggers the null pointer dereference?
The issue can occur when devcoredump cleanup runs for a snapshot that was never fully populated, leaving ss->gt as NULL. This can happen when cleanup is triggered without a prior capture.
Is deferred-work cleanup always involved?
No. Deferred work is only queued when a coredump has been captured. The fix avoids calling cancel_work_sync() unless coredump->captured is set.
How can I determine whether the relevant fixes are present?
Check whether your kernel includes the stable commits f5c3144f783f91d74b4fae84fb8bd7a4edf001f8 and 12ef528d78adc8ea4e7e3db594f3bcac327e79fa.