CVE-2026-23467

In the Linux kernel, the following vulnerability has been resolved: drm/i915/dmc: Fix an unlikely NULL pointer deference at probe intel_dmc_update_dc6_allowed_count() oopses when DMC hasn't been initialized, and dmc is thus NULL. That would be the case when the call path is intel_power_domains_init_hw() -> {skl,bxt,icl}_display_core_init() -> gen9_set_dc_state() -> intel_dmc_update_dc6_allowed_count(), as intel_power_domains_init_hw() is called *before* intel_dmc_init(). However, gen9_set_dc_state() calls intel_dmc_update_dc6_allowed_count() conditionally, depending on the current and target DC states. At probe, the target is disabled, but if DC6 is enabled, the function is called, and an oops follows. Apparently it's quite unlikely that DC6 is enabled at probe, as we haven't seen this failure mode before. It is also strange to have DC6 enabled at boot, since that would require the DMC firmware (loaded by BIOS); the BIOS loading the DMC firmware and the driver stopping / reprogramming the firmware is a poorly specified sequence and as such unlikely an intentional BIOS behaviour. It's more likely that BIOS is leaving an unintentionally enabled DC6 HW state behind (without actually loading the required DMC firmware for this). The tracking of the DC6 allowed counter only works if starting / stopping the counter depends on the _SW_ DC6 state vs. the current _HW_ DC6 state (since stopping the counter requires the DC5 counter captured when the counter was started). Thus, using the HW DC6 state is incorrect and it also leads to the above oops. Fix both issues by using the SW DC6 state for the tracking. This is v2 of the fix originally sent by Jani, updated based on the first Link: discussion below. (cherry picked from commit 2344b93af8eb5da5d496b4e0529d35f0f559eaf0)

• CWE-476

• https://git.kernel.org/stable/c/0b35d11fbbcfd1079c8489282a341944228835e3Patch
• https://git.kernel.org/stable/c/631317825d44283abfe7a8374f13a76ce2032bb8Patch
• https://git.kernel.org/stable/c/ac57eb3b7d2ad649025b5a0fa207315f755ac4f6Patch

Published

Apr 3, 2026

Last Modified

Jul 24, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-23461In the Linux kernel, the following vulnerability has been re…8.8
• CVE-2026-23462In the Linux kernel, the following vulnerability has been re…8.8
• CVE-2026-23463In the Linux kernel, the following vulnerability has been re…4.7
• CVE-2026-23464In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-23465In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-23466In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-23468In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-23469In the Linux kernel, the following vulnerability has been re…4.7
• CVE-2026-2347Authorization bypass through User-Controlled key vulnerabili…9.8
• CVE-2026-23470In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-23471Rejected reason: This CVE ID has been rejected or withdrawn …
• CVE-2026-23472In the Linux kernel, the following vulnerability has been re…5.5