drm/xe: Fix null pointer dereference in devcoredump cleanup
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.53
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/xe: Fix null pointer dereference in devcoredump cleanup In xe_devcoredump_snapshot_free(), ss->gt may be NULL when the snapshot was never fully populated (e.g., when cleanup is triggered without a prior capture). Guard the xe_guc_capture_put_matched_nodes() call with IS_ERR_OR_NULL() to prevent a null dereference. In xe_devcoredump_free(), the deferred work is only queued when a coredump is captured, so guard cancel_work_sync() with a check on coredump->captured.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From ecb6336463911d6eb684998754f8701d0f437f18 · fixed in f5c3144f783f91d74b4fae84fb8bd7a4edf001f8; From ecb6336463911d6eb684998754f8701d0f437f18 · fixed in 12ef528d78adc8ea4e7e3db594f3bcac327e79fa
- Linux Linux
6.13
- KernelLinux
From 6.13.0 · fixed in 6.18.53