linux: In the Linux kernel, the following vulnerability has been resolved: drm/i915/vrr: Configure VRR timings after enabli...
CVE-2026-43477 is fixed in 23 products on 1 platform, first by ALAS2023-2026-1596, released April 27, 2026. It is not reported as exploited. Patch Radar priority: Routine.
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)
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| bpftool6.18 · amzn 2023 | 1:6.18.20-20.229.amzn2023 | ALAS2023-2026-1596 | Apr 27, 2026 |
| bpftool6.18-debuginfo · amzn 2023 | 1:6.18.20-20.229.amzn2023 | ALAS2023-2026-1596 | Apr 27, 2026 |
| kernel-livepatch-6.18.20-20.229 · amzn 2023 | 1:1.0-0.amzn2023 | ALAS2023-2026-1596 | Apr 27, 2026 |
| kernel6.18 · amzn 2023 | 1:6.18.20-20.229.amzn2023 | ALAS2023-2026-1596 | Apr 27, 2026 |
| kernel6.18-debuginfo · amzn 2023 | 1:6.18.20-20.229.amzn2023 | ALAS2023-2026-1596 | Apr 27, 2026 |
| kernel6.18-debuginfo-common-aarch64 · amzn 2023 | 1:6.18.20-20.229.amzn2023 | ALAS2023-2026-1596 | Apr 27, 2026 |
| kernel6.18-debuginfo-common-x86_64 · amzn 2023 | 1:6.18.20-20.229.amzn2023 | ALAS2023-2026-1596 | Apr 27, 2026 |
| kernel6.18-devel · amzn 2023 | 1:6.18.20-20.229.amzn2023 | ALAS2023-2026-1596 | Apr 27, 2026 |
| kernel6.18-headers · amzn 2023 | 1:6.18.20-20.229.amzn2023 | ALAS2023-2026-1596 | Apr 27, 2026 |
| kernel6.18-libbpf · amzn 2023 | 1:6.18.20-20.229.amzn2023 | ALAS2023-2026-1596 | Apr 27, 2026 |
| kernel6.18-libbpf-debuginfo · amzn 2023 | 1:6.18.20-20.229.amzn2023 | ALAS2023-2026-1596 | Apr 27, 2026 |
| kernel6.18-libbpf-devel · amzn 2023 | 1:6.18.20-20.229.amzn2023 | ALAS2023-2026-1596 | Apr 27, 2026 |
| kernel6.18-libbpf-static · amzn 2023 | 1:6.18.20-20.229.amzn2023 | ALAS2023-2026-1596 | Apr 27, 2026 |
| kernel6.18-modules-extra · amzn 2023 | 1:6.18.20-20.229.amzn2023 | ALAS2023-2026-1596 | Apr 27, 2026 |
| kernel6.18-modules-extra-common · amzn 2023 | 1:6.18.20-20.229.amzn2023 | ALAS2023-2026-1596 | Apr 27, 2026 |
| kernel6.18-tools · amzn 2023 | 1:6.18.20-20.229.amzn2023 | ALAS2023-2026-1596 | Apr 27, 2026 |
| kernel6.18-tools-debuginfo · amzn 2023 | 1:6.18.20-20.229.amzn2023 | ALAS2023-2026-1596 | Apr 27, 2026 |
| kernel6.18-tools-devel · amzn 2023 | 1:6.18.20-20.229.amzn2023 | ALAS2023-2026-1596 | Apr 27, 2026 |
| linux · Debian 14 | 6.19.10-1 | DEBIAN-CVE-2026-43477 | May 15, 2026 |
| perf6.18 · amzn 2023 | 1:6.18.20-20.229.amzn2023 | ALAS2023-2026-1596 | Apr 27, 2026 |
| perf6.18-debuginfo · amzn 2023 | 1:6.18.20-20.229.amzn2023 | ALAS2023-2026-1596 | Apr 27, 2026 |
| python3-perf6.18 · amzn 2023 | 1:6.18.20-20.229.amzn2023 | ALAS2023-2026-1596 | Apr 27, 2026 |
| python3-perf6.18-debuginfo · amzn 2023 | 1:6.18.20-20.229.amzn2023 | ALAS2023-2026-1596 | Apr 27, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.