drm/xe/guc: Keep scheduler timeline name alive
- 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.12.114, 6.16, 6.17, 6.18.57, 7.1.6
- 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/xe/guc: Keep scheduler timeline name alive The scheduler keeps a pointer to the timeline name, but q->name is freed with the exec queue while scheduler fences can still reference it. Store the name in struct xe_guc_exec_queue so it shares the scheduler's RCU-deferred lifetime. (cherry picked from commit 41075f0eb5dcbd3b065d15f15ef7bbe9315188e8)
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From b17fcce70733c211cb5dabf54f4f9491920b1d92 · fixed in eac2839585741e6c1b4af261a0b58bca0d6f5436; From 6bd90e700b4285e6a7541e00f969cab0d696adde · fixed in 88c38ff74f8345fcf8852549f94025754019b037; From 6bd90e700b4285e6a7541e00f969cab0d696adde · fixed in 77fd62412431e8c80ef2ad61466bc76fe425f80a; From 6bd90e700b4285e6a7541e00f969cab0d696adde · fixed in 299bc6d50b1bed7d1f408391736712f01a0855e2; From 6.12.43 · fixed in 6.12.114; From 6.15.11 · fixed in 6.16; From 6.16.2 · fixed in 6.17
- Linux Linux
6.17
- KernelLinux
fixed in 6.12.114; From 6.13.0 · fixed in 6.18.57; From 6.17.0 · fixed in 7.1.6