# CVE-2026-68241: drm/i915/mst: limit DP MST ESI service loop

> An unbounded loop in the Intel i915 DP MST driver allows a malicious sink device to cause a denial of service by keeping the kernel busy servicing interrupts.

- **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:** 10 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-94938, BELL-CVE-2026-68241, DEBIAN-CVE-2026-68241, GHSA-334r-pfv9-rpmj, UBUNTU-CVE-2026-68241

## What is CVE-2026-68241?

CVE-2026-68241 is a denial of service vulnerability in Linux, published on 10 Aug 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/i915/mst: limit DP MST ESI service loop

The loop in intel_dp_check_mst_status() keeps servicing interrupts
originating from the sink without bound. Add an upper bound to the new
interrupts occurring during interrupt processing to not get stuck on
potentially stuck sink devices. Use arbitrary 32 tries to clear incoming
interrupts in one go.

Discovered using AI-assisted static analysis confirmed by Intel Product
Security.

Note: The condition likely pre-dates the commit in the Fixes: tag, but
this is about as far back as a backport has any chance of
succeeding. Before that, the retry had a goto.

(cherry picked from commit b4ea5272133059acb493cc36599071a9e852ec2e)

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


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

Apply the vendor's patch.

## Is CVE-2026-68241 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68241 is a denial of service vulnerability in Linux, published on 10 Aug 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-68241 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-68241/ (Markdown: https://insights.sbomify.com/CVE-2026-68241/index.md)
```

## Sources

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

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