CVE-2026-93058
Last modified
CVE-2026-93058 is a vulnerability of currently unknown severity. 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/.
Description
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/
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19, < d43e1bbfd43458b9242806eec77ea3b032134baf; >= 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19, < 09b360eb6ce345996a30fad8c86e9df80f41cd7e; >= 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19, < e2332abed2a4d3caa59052095dc16e4ce44791ea |
| Linux | Linux | 5.15 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-93058?
How severe is CVE-2026-93058?
How do I fix CVE-2026-93058?
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 2026
- CVE-2026-93052In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93053In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93054In the Linux kernel, the following vulnerability has been re…7
- CVE-2026-93055In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93056In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93057In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93059In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9306A security vulnerability has been detected in QuantumNous ne…3.7
- CVE-2026-93060In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93061In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93062In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93063In the Linux kernel, the following vulnerability has been re…8.4
Are you affected by CVE-2026-93058?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
