Answer in brief
CVE-2026-43477 records a Medium severity (CVSS 5.5) vulnerability in drm/i915/vrr: Configure VRR timings after enabling TRANS_DDI_FUNC_CTL. 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.
CVSS is 5.5. 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 | >=dda7dcd9da73c5327aef42b89f0519bb51e84217 <8a7d29b8bda144d44e61df1b2705b1d4378f4e44 || >=dda7dcd9da73c5327aef42b89f0519bb51e84217 <bf9e3b6ffd76da38dd4961c65d80571b25bf10a5 || >=dda7dcd9da73c5327aef42b89f0519bb51e84217 <237aab549676288d9255bb8dcc284738e56eaa31 | 8a7d29b8bda144d44e61df1b2705b1d4378f4e44, bf9e3b6ffd76da38dd4961c65d80571b25bf10a5, 237aab549676288d9255bb8dcc284738e56eaa31 |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
May 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 26, 2026
In the Linux kernel, the following vulnerability has been resolved: drm/i915/vrr: Configure VRR timings after enabling TRANS_DDI_FUNC_CTL Apparently ICL may hang with an MCE if we write TRANS_VRR_VMAX/FLIPLINE before enabling TRANS_DDI_FUNC_CTL. Personally I was only able to reproduce a hang (on an Dell XPS 7390 2-in-1) with an external display connected via a dock using a dodgy type-C cable that made the link training fail. After the failed link training the machine would hang. TGL seemed immune to the problem for whatever reason. BSpec does tell us to configure VRR after enabling TRANS_DDI_FUNC_CTL as well. The DMC firmware also does the VRR restore in two stages: - first stage seems to be unconditional and includes TRANS_VRR_CTL and a few other VRR registers, among other things - second stage is conditional on the DDI being enabled, and includes TRANS_DDI_FUNC_CTL and TRANS_VRR_VMAX/VMIN/FLIPLINE, among other things So let's reorder the steps to match to avoid the hang, and toss in an extra WARN to make sure we don't screw this up later. BSpec: 22243 (cherry picked from commit 93f3a267c3dd4d811b224bb9e179a10d81456a74)
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-43477 records a Medium severity (CVSS 5.5) vulnerability in drm/i915/vrr: Configure VRR timings after enabling TRANS_DDI_FUNC_CTL. 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.
CVSS is 5.5. 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 | >=dda7dcd9da73c5327aef42b89f0519bb51e84217 <8a7d29b8bda144d44e61df1b2705b1d4378f4e44 || >=dda7dcd9da73c5327aef42b89f0519bb51e84217 <bf9e3b6ffd76da38dd4961c65d80571b25bf10a5 || >=dda7dcd9da73c5327aef42b89f0519bb51e84217 <237aab549676288d9255bb8dcc284738e56eaa31 | 8a7d29b8bda144d44e61df1b2705b1d4378f4e44, bf9e3b6ffd76da38dd4961c65d80571b25bf10a5, 237aab549676288d9255bb8dcc284738e56eaa31 |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
May 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 26, 2026
In the Linux kernel, the following vulnerability has been resolved: drm/i915/vrr: Configure VRR timings after enabling TRANS_DDI_FUNC_CTL Apparently ICL may hang with an MCE if we write TRANS_VRR_VMAX/FLIPLINE before enabling TRANS_DDI_FUNC_CTL. Personally I was only able to reproduce a hang (on an Dell XPS 7390 2-in-1) with an external display connected via a dock using a dodgy type-C cable that made the link training fail. After the failed link training the machine would hang. TGL seemed immune to the problem for whatever reason. BSpec does tell us to configure VRR after enabling TRANS_DDI_FUNC_CTL as well. The DMC firmware also does the VRR restore in two stages: - first stage seems to be unconditional and includes TRANS_VRR_CTL and a few other VRR registers, among other things - second stage is conditional on the DDI being enabled, and includes TRANS_DDI_FUNC_CTL and TRANS_VRR_VMAX/VMIN/FLIPLINE, among other things So let's reorder the steps to match to avoid the hang, and toss in an extra WARN to make sure we don't screw this up later. BSpec: 22243 (cherry picked from commit 93f3a267c3dd4d811b224bb9e179a10d81456a74)
Quoted source text, attributed separately from HOL analysis.