https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 09 Oct 2026 17:48:32 +0000 https://cve.radiocsirt.org/vuln/cve-2025-38369 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dmaengine: idxd: Check availability of workqueue allocated by idxd wq driver before using</p> <p>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.</p> <p>This issue occurs because, under certain configurations, Docker does not properly propagate the mount replica back to the original mount point.</p> <p>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&#39;s necessary to check wq-&gt;wq and skip the drain if it no longer exists.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dmaengine: idxd: Check availability of workqueue allocated by idxd wq driver before using</p> <p>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.</p> <p>This issue occurs because, under certain configurations, Docker does not properly propagate the mount replica back to the original mount point.</p> <p>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&#39;s necessary to check wq-&gt;wq and skip the drain if it no longer exists.</p> https://cve.radiocsirt.org/vuln/cve-2025-38369