Answer in brief
CVE-2026-68241 records a Unknown severity vulnerability in drm/i915/mst: limit DP MST ESI service loop. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3c0ec2c2d5948356a22c8f1c08a8087b12a303e7 <e3bcd3bf7eeca9570b9fa0b2f8a602c7bcc6b0d0 || >=3c0ec2c2d5948356a22c8f1c08a8087b12a303e7 <9061fbf2230b6fcef042a6f637beae57c2fc93a5 || >=3c0ec2c2d5948356a22c8f1c08a8087b12a303e7 <005771c18c5b2c98cb4e7517661aea460990fd3f | e3bcd3bf7eeca9570b9fa0b2f8a602c7bcc6b0d0, 9061fbf2230b6fcef042a6f637beae57c2fc93a5, 005771c18c5b2c98cb4e7517661aea460990fd3f |
| Linux/Linuxgeneric | 5.8 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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)
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68241 records a Unknown severity vulnerability in drm/i915/mst: limit DP MST ESI service loop. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3c0ec2c2d5948356a22c8f1c08a8087b12a303e7 <e3bcd3bf7eeca9570b9fa0b2f8a602c7bcc6b0d0 || >=3c0ec2c2d5948356a22c8f1c08a8087b12a303e7 <9061fbf2230b6fcef042a6f637beae57c2fc93a5 || >=3c0ec2c2d5948356a22c8f1c08a8087b12a303e7 <005771c18c5b2c98cb4e7517661aea460990fd3f | e3bcd3bf7eeca9570b9fa0b2f8a602c7bcc6b0d0, 9061fbf2230b6fcef042a6f637beae57c2fc93a5, 005771c18c5b2c98cb4e7517661aea460990fd3f |
| Linux/Linuxgeneric | 5.8 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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)
Quoted source text, attributed separately from HOL analysis.