Finding and attribution
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... Per the CNA record; severity and exploitation not independently assessed.
Product: Linux Linux. AI system: AI-assisted static analysis (tool not named). Team / organization: Linux kernel maintainers.
CVE identifiers: CVE-2026-68241.
AI and human contribution (source account): The upstream commit message says: "Discovered using AI-assisted static analysis confirmed by Intel Product Security". The CVE description reproduces the commit message; the model and human validation are not further documented.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The cited records establish a public disclosure and the stated AI contribution. They do not establish exploitation in the wild or a zero-day incident.
Remediation status: fix documented. The CVE record or its linked advisory describes a fixed/upgrade version or patch; deployed patch status is not checked.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 10 Aug 2026. AI attribution date not established by the source. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Not available · no assessment established here. Documented technical effects: Not available.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
No source-backed CVSS assessment is established in this catalog.
Technical effects, prerequisites and exploitation evidence are not established here. Missing evidence does not establish absence of exploitation.
Documented fix: The CVE record or its linked advisory describes a fixed/upgrade version or patch; deployed patch status is not checked.