CVE-2025-38356: drm/xe/guc: Explicitly exit CT safe mode on unwind

Published Jul 25, 2025
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

drm/xe/guc: Explicitly exit CT safe mode on unwind

During driver probe we might be briefly using CT safe mode, which is based on a delayed work, but usually we are able to stop this once we have IRQ fully operational. However, if we abort the probe quite early then during unwind we might try to destroy the workqueue while there is still a pending delayed work that attempts to restart itself which triggers a WARN.

This was recently observed during unsuccessful VF initialization:

[ ] xe 0000:00:02.1: probe with driver xe failed with error -62 [ ] ------------[ cut here ]------------ [ ] workqueue: cannot queue safemodeworkerfunc [xe] on wq xe-g2h-wq [ ] WARNING: CPU: 9 PID: 0 at kernel/workqueue.c:2257 queuework+0x287/0x710 [ ] RIP: 0010:queuework+0x287/0x710 [ ] Call Trace: [ ] delayedworktimerfn+0x19/0x30 [ ] calltimerfn+0xa1/0x2a0

Exit the CT safe mode on unwind to avoid that warning.

(cherry picked from commit 2ddbb73ec20b98e70a5200cb85deade22ccea2ec)

Affected Software

11 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=6.11<6.12.37
Linux Linux kernel>=6.13<6.15.5
Linux Linux kernel=6.16-rc1
Linux Linux kernel=6.16-rc2
Linux Linux kernel=6.16-rc3
debian/linux<6.12.37-1
6.12.37-1
debian/linux<6.12.37-1
6.12.37-1
linux/kernel>=6.11.0<6.12.37
6.12.37
linux/kernel>=6.13.0<6.15.5
6.15.5
debian/linux
6.1.176-16.1.190-16.12.107-16.12.115-27.2.15-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.12.37-1
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.37
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.15.5
  4. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.115-2Fixed in 7.2.15-1
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch 2ddbb73ec20b98e70a5200cb85deade22ccea2ec

Event History

Jul 25, 2025
CVE Published
via MITRE·12:47 PM
Data Sourced
via MITRE·12:47 PM
Description
Data Sourced
via OSV·12:47 PM
DescriptionAffected Software
Data Sourced
via NVD·01:15 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via OSV·01:15 PM
Severity

Frequently Asked Questions

1

What is the severity of CVE-2025-38356?

CVE-2025-38356 has been categorized with a specific severity level, which typically indicates the potential impact on systems using the Linux kernel.

2

How do I fix CVE-2025-38356?

To mitigate CVE-2025-38356, updating the Linux kernel to the latest patched version is recommended.

3

What systems are affected by CVE-2025-38356?

CVE-2025-38356 affects systems running the Linux kernel, particularly those utilizing the drm/xe/guc module.

4

What is the impact of CVE-2025-38356 on Linux kernel performance?

CVE-2025-38356 may briefly affect performance due to the use of CT safe mode during the driver probe process.

5

Is CVE-2025-38356 exploitative in nature?

CVE-2025-38356 does not specifically indicate exploitability but addresses a mode of safe operation during driver initialization.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203