CVE-2025-38369
Last modified
CVE-2025-38369 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Check availability of workqueue allocated by idxd wq driver before using Running IDXD workloads in a container with the /dev directory mounted can trigger a call trace or even a kernel panic when the parent process of the container is terminated. This issue occurs because, under certain configurations, Docker does not properly propagate the mount replica back to the original mount point. In this case, when the user driver detaches, the WQ is destroyed but it still calls destroy_workqueue() attempting to completes all pending work. It's necessary to check wq->wq and skip the drain if it no longer exists.. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Check availability of workqueue allocated by idxd wq driver before using Running IDXD workloads in a container with the /dev directory mounted can trigger a call trace or even a kernel panic when the parent process of the container is terminated. This issue occurs because, under certain configurations, Docker does not properly propagate the mount replica back to the original mount point. In this case, when the user driver detaches, the WQ is destroyed but it still calls destroy_workqueue() attempting to completes all pending work. It's necessary to check wq->wq and skip the drain if it no longer exists.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 5.6, < 6.6.96 |
| Linux | Linux Kernel | >= 6.7, < 6.12.36 |
| Linux | Linux Kernel | >= 6.13, < 6.15.5 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2025-38369?
How severe is CVE-2025-38369?
How do I fix CVE-2025-38369?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-38363In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38364In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38365In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2025-38366In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38367In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38368In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-3837An improper input validation vulnerability is identified in …6.1
- CVE-2025-38370In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38371In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38372In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38373In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38374In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2025-38369?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
