CVE-2026-68241: drm/i915/mst: limit DP MST ESI service loop
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Fixed version: Linux Linux 005771c18c5b2c98cb4e7517661aea460990fd3f, 02ceba559412751106c0cfa5cbdb80db50303083, 9061fbf2230b6fcef042a6f637beae57c2fc93a5; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 005771c18c5b2c98cb4e7517661aea460990fd3f, 02ceba559412751106c0cfa5cbdb80db50303083, 9061fbf2230b6fcef042a6f637beae57c2fc93a5; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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)
- Published
- Aug 10, 2026
- Updated
- Oct 21, 2026
- EPSS
- 0.2% · 9th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.8affected
- 3c0ec2c2d5948356a22c8f1c08a8087b12a303e7 and later · before fae63319ad397666a9c56a17ea1047d2bf9a1e25affected · git
- 3c0ec2c2d5948356a22c8f1c08a8087b12a303e7 and later · before 02ceba559412751106c0cfa5cbdb80db50303083affected · git
- 3c0ec2c2d5948356a22c8f1c08a8087b12a303e7 and later · before e3bcd3bf7eeca9570b9fa0b2f8a602c7bcc6b0d0affected · git
- 3c0ec2c2d5948356a22c8f1c08a8087b12a303e7 and later · before 9061fbf2230b6fcef042a6f637beae57c2fc93a5affected · git
- 3c0ec2c2d5948356a22c8f1c08a8087b12a303e7 and later · before 005771c18c5b2c98cb4e7517661aea460990fd3faffected · git
- before 5.8not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
- 6.12.114 and later · up to and including 6.12.*not affected · semver
- 6.18.42 and later · up to and including 6.18.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:14 | linux | before 7.1.6-1 | 7.1.6-1 |
| openSUSE:Leap 16.0 | dtb-aarch64 | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| openSUSE:Leap 16.0 | kernel-64kb | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| openSUSE:Leap 16.0 | kernel-azure | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| openSUSE:Leap 16.0 | kernel-default | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| openSUSE:Leap 16.0 | kernel-default-base | before 6.12.0-160000.40.1.160000.2.29 | 6.12.0-160000.40.1.160000.2.29 |
| openSUSE:Leap 16.0 | kernel-docs | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| openSUSE:Leap 16.0 | kernel-kvmsmall | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| openSUSE:Leap 16.0 | kernel-obs-build | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| openSUSE:Leap 16.0 | kernel-obs-qa | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| openSUSE:Leap 16.0 | kernel-rt | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| openSUSE:Leap 16.0 | kernel-source | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| openSUSE:Leap 16.0 | kernel-syms | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
| openSUSE:Leap 16.0 | kernel-zfcpdump | before 6.12.0-160000.40.1 | 6.12.0-160000.40.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-68238Aug 10, 2026 · drm/amdgpu: Release VFCT ACPI table reference0Monitor
- ← EarlierCVE-2026-68240Aug 10, 2026 · drm/gpusvm: publish dpagemap early to avoid device mapping leak on error35Monitor
- Later →CVE-2026-68242Aug 10, 2026 · drm/i915/gt: Fix NULL deref on sched_engine alloc failure0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 005771c18c5b2c98cb4e7517661aea460990fd3f | Vendor (CNA) |
| Linux Linux | 02ceba559412751106c0cfa5cbdb80db50303083 | Vendor (CNA) |
| Linux Linux | 9061fbf2230b6fcef042a6f637beae57c2fc93a5 | Vendor (CNA) |
| Linux Linux | e3bcd3bf7eeca9570b9fa0b2f8a602c7bcc6b0d0 | Vendor (CNA) |
| Linux Linux | fae63319ad397666a9c56a17ea1047d2bf9a1e25 | Vendor (CNA) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 7.1.6-1 · Debian:14 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.12.0-160000.40.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.12.0-160000.40.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-azure | 6.12.0-160000.40.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default | 6.12.0-160000.40.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.12.0-160000.40.1.160000.2.29 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-docs | 6.12.0-160000.40.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.12.0-160000.40.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.12.0-160000.40.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-qa | 6.12.0-160000.40.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-rt | 6.12.0-160000.40.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-source | 6.12.0-160000.40.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-syms | 6.12.0-160000.40.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.