# CVE-2026-93058: drm/msm: Only fini scheduler after successful init

> A local attacker can cause a kernel crash by triggering a failure in the MSM DRM driver initialization, leading to a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-102188, BELL-CVE-2026-93058, DEBIAN-CVE-2026-93058, GHSA-2m9v-9vx7-p7w7, UBUNTU-CVE-2026-93058

## What is CVE-2026-93058?

CVE-2026-93058 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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/

## Which versions are affected by CVE-2026-93058?


## How do I fix CVE-2026-93058?

Apply the vendor's patch.

## Is CVE-2026-93058 being exploited?

There is no known exploitation of CVE-2026-93058 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93058 and fix it if it is affected.

What it is: CVE-2026-93058 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93058 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93058/ (Markdown: https://insights.sbomify.com/CVE-2026-93058/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93058
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93058
- OSV: https://osv.dev/vulnerability/CVE-2026-93058

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93058/
Summaries are generated and may contain mistakes; the official description above is the record.