Medium [CVE-2026-68241] limit DP MST ESI service loop
This medium-severity Red Hat Linux advisory covers CVE-2026-68241 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
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) A flaw was found in the Linux kernel's DisplayPort Multi-Stream Transport (MST) subsystem.
An unbounded loop in the `intel_dp_check_mst_status()` function, responsible for servicing interrupts from a sink device, can lead to a system becoming unresponsive. A malicious or faulty DisplayPort MST sink device could exploit this to trigger a Denial of Service (DoS) condition.
This issue affects systems using Intel i915 DisplayPort MST. intel_dp_check_mst_status() could loop indefinitely servicing sink interrupts from a stuck device, causing soft lockup. Systems without Intel graphics or DP MST are not affected.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 2 days ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 2 days ago·verify at source
Mitigation checklist
- To mitigate this issue, prevent the i915 module from loading. See https://access.redhat.com/solutions/41278 for instructions.
Official advisory · high-confidence parse· fetched 2 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.