https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 15:21:12 +0000 https://vulnerability.circl.lu/vuln/bell-cve-2026-93058 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://vulnerability.circl.lu/vuln/bell-cve-2026-93058 https://vulnerability.circl.lu/vuln/fkie_cve-2026-93058 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/msm: Only fini scheduler after successful init</p> <p>msm_ringbuffer_new() destroys a partially initialized ring through msm_ringbuffer_destroy() when an allocation or scheduler setup step fails.</p> <p>If drm_sched_init() fails before it finishes initializing the scheduler, the failure path still calls drm_sched_fini(). That teardown path assumes the scheduler work items, lists, and workqueue state were initialized.</p> <p>Track successful scheduler initialization and call drm_sched_fini() only after drm_sched_init() returned 0.</p> <p>This issue was found by a static analysis checker and confirmed by manual source review.</p> <p>Patchwork: https://patchwork.freedesktop.org/patch/738905/</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/msm: Only fini scheduler after successful init</p> <p>msm_ringbuffer_new() destroys a partially initialized ring through msm_ringbuffer_destroy() when an allocation or scheduler setup step fails.</p> <p>If drm_sched_init() fails before it finishes initializing the scheduler, the failure path still calls drm_sched_fini(). That teardown path assumes the scheduler work items, lists, and workqueue state were initialized.</p> <p>Track successful scheduler initialization and call drm_sched_fini() only after drm_sched_init() returned 0.</p> <p>This issue was found by a static analysis checker and confirmed by manual source review.</p> <p>Patchwork: https://patchwork.freedesktop.org/patch/738905/</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-93058 https://vulnerability.circl.lu/vuln/ghsa-2m9v-9vx7-p7w7 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/msm: Only fini scheduler after successful init</p> <p>msm_ringbuffer_new() destroys a partially initialized ring through msm_ringbuffer_destroy() when an allocation or scheduler setup step fails.</p> <p>If drm_sched_init() fails before it finishes initializing the scheduler, the failure path still calls drm_sched_fini(). That teardown path assumes the scheduler work items, lists, and workqueue state were initialized.</p> <p>Track successful scheduler initialization and call drm_sched_fini() only after drm_sched_init() returned 0.</p> <p>This issue was found by a static analysis checker and confirmed by manual source review.</p> <p>Patchwork: https://patchwork.freedesktop.org/patch/738905/</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/msm: Only fini scheduler after successful init</p> <p>msm_ringbuffer_new() destroys a partially initialized ring through msm_ringbuffer_destroy() when an allocation or scheduler setup step fails.</p> <p>If drm_sched_init() fails before it finishes initializing the scheduler, the failure path still calls drm_sched_fini(). That teardown path assumes the scheduler work items, lists, and workqueue state were initialized.</p> <p>Track successful scheduler initialization and call drm_sched_fini() only after drm_sched_init() returned 0.</p> <p>This issue was found by a static analysis checker and confirmed by manual source review.</p> <p>Patchwork: https://patchwork.freedesktop.org/patch/738905/</p> https://vulnerability.circl.lu/vuln/ghsa-2m9v-9vx7-p7w7 https://vulnerability.circl.lu/vuln/msrc_cve-2026-93058 msrc_CVE-2026-93058 https://vulnerability.circl.lu/vuln/msrc_cve-2026-93058 https://vulnerability.circl.lu/vuln/opensuse-su-2026:11893-1 <p>kernel-devel-7.2.8-1.1 on GA media</p> <p>kernel-devel-7.2.8-1.1 on GA media</p> https://vulnerability.circl.lu/vuln/opensuse-su-2026:11893-1 https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-93058 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 193 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: drm/msm: Only fini scheduler after successful init msm_ringbuffer_new() destroys a partially initialized ring through msm_ringbuffer_destroy() when an allocation or scheduler setup step fails. If drm_sched_init() fails before it finishes initializing the scheduler, the failure path still calls drm_sched_fini(). That teardown path assumes the scheduler work items, lists, and workqueue state were initialized. Track successful scheduler initialization and call drm_sched_fini() only after drm_sched_init() returned 0. This issue was found by a static analysis checker and confirmed by manual source review. Patchwork: https://patchwork.freedesktop.org/patch/738905/</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 193 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: drm/msm: Only fini scheduler after successful init msm_ringbuffer_new() destroys a partially initialized ring through msm_ringbuffer_destroy() when an allocation or scheduler setup step fails. If drm_sched_init() fails before it finishes initializing the scheduler, the failure path still calls drm_sched_fini(). That teardown path assumes the scheduler work items, lists, and workqueue state were initialized. Track successful scheduler initialization and call drm_sched_fini() only after drm_sched_init() returned 0. This issue was found by a static analysis checker and confirmed by manual source review. Patchwork: https://patchwork.freedesktop.org/patch/738905/</p> https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-93058