CVE-2024-58074 | drm/i915: Grab intel_display from the encoder to avoid potential oopsies

In the Linux kernel, the following vulnerability has been resolved: drm/i915: Grab intel_display from the encoder to avoid potential oopsies Grab the intel_display from 'encoder' rather than 'state' in the encoder hooks to avoid the massive footgun that is intel_sanitize_encoder(), which passes NULL as the 'state' argument to encoder .disable() and .post_disable(). TODO: figure out how to actually fix intel_sanitize_encoder()...

Published: 2025-03-06 Last update: 2025-10-31 Assigner: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Conclusion & alert: CVE-2024-58074 is rated Low Risk (25.6/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.04%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-58074

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-01 0.05% 0.04% -0.01%
2 2025-09-30 0.05% 0.05% +0.00%
3 2025-08-21 0.05%

Full EPSS history (5 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-58074

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.8 3.6 [email protected]

Weakness enumeration for CVE-2024-58074

OS Trackers for CVE-2024-58074

vendor priority summary link
debian unimportant CVE-2024-58074 unimportant priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2024-58074
redhat low https://access.redhat.com/security/cve/CVE-2024-58074
suse medium CVE-2024-58074 severity moderate: SUSE including 76 source package names (15.7.20.5.1:kernel-default-6.4.0-150700.53.3.1, cluster-md-kmp-default, …), 396 product×package rows across 95 product lines (Container suse/hpc/warewulf4-x86_64/sle-hpc-node, Image SLES15-SP7-Azure-3P, … (95 product lines)): Known Not Affected 245, Fixed 151. https://www.suse.com/security/cve/CVE-2024-58074/
ubuntu medium CVE-2024-58074 medium priority: Ubuntu including 128 source packages (linux, linux-allwinner-5.19, …), 1024 status rows across 8 suites (bionic, focal, jammy, noble, oracular, trusty, upstream, xenial): DNE 702, ignored 146, not-affected 114, released 62. https://ubuntu.com/security/CVE-2024-58074

Affected software / configurations for CVE-2024-58074

Vendor Product Version Raw CPE
linux linux_kernel >= 6.12, < 6.13.2 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

References for CVE-2024-58074

cvelogic Threat Intelligence