🛡️ CVE-2025-68326 — kernel
Description
drm/xe/guc: Fix stack_depot usage
In the Linux kernel, the following vulnerability has been resolved:
drm/xe/guc: Fix stack_depot usage
Add missing stack_depot_init() call when CONFIG_DRM_XE_DEBUG_GUC is
enabled to fix the following call stack:
[] BUG: kernel NULL pointer dereference, address: 0000000000000000
[] Workqueue: drm_sched_run_job_work [gpu_sched]
[] RIP: 0010:stack_depot_save_flags+0x172/0x870
[] Call Trace:
[] <TASK>
[] fast_req_track+0x58/0xb0 [xe]
(cherry picked from commit 64fdf496a6929a0a194387d2bb5efaf5da2b542f)
Affected software
CVE-2025-68326 is recorded against 2 packages.
- kernel (from 6.17.0 up to 6.17.11)
- unknown
Timeline and source
Published on 22 December 2025 and last revised on 15 July 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.
References
git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)
CVE-2025-68326 on other distributions
Each distribution ships its own build and its own fixed version. Pick the one you run:
Details
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| kernel | 6.17.0 | 6.17.11 |
| unknown | — | — |
References
Similar Threats
- Unknown ALBA-2026:39332
- Unknown ALSA-2023:1703
- Unknown ALSA-2023:1566
- Unknown ALSA-2023:1470
- Unknown ALSA-2023:0951
Free Vulnerability Check
Is your site affected by CVE-2025-68326?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against CVE-2025-68326 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.