VulnerabilityPublished 28 Oct 2026

CVE-2026-99146: Linux kernel · drm/i915/dmc: Add sanity check for DMC load address

Source GCVE Database

Authoritative record:CVE-2026-99146

Not known to be exploited · fixed in ef82b4d5cb4a3fe77c7f99008d78b8c64709e258 : update Linux kernel when convenient.

Data as of 28 Oct 2026, 14:01 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Patch: Available – fixed in ef82b4d5cb4a3fe77c7f99008d78b8c64709e258, 7dedc5bb11f95e96fe80757c924d8d9aa7327759, 2fbd099b4e7c8c4ff70033c5bb950cdbb20838e2

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-p734-mrrw-8qv9

What to do

Upgrade Linux kernel to ef82b4d5cb4a3fe77c7f99008d78b8c64709e258, 7dedc5bb11f95e96fe80757c924d8d9aa7327759 or 2fbd099b4e7c8c4ff70033c5bb950cdbb20838e2.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 3d5928a168a9546b23c6b3439c6158d7a028326c, < ef82b4d5cb4a3fe77c7f99008d78b8c64709e258	Fixed in ef82b4d5cb4a3fe77c7f99008d78b8c64709e258
LinuxLinux	Affected ≥ 3d5928a168a9546b23c6b3439c6158d7a028326c, < 7dedc5bb11f95e96fe80757c924d8d9aa7327759	Fixed in 7dedc5bb11f95e96fe80757c924d8d9aa7327759
LinuxLinux	Affected ≥ 3d5928a168a9546b23c6b3439c6158d7a028326c, < 2fbd099b4e7c8c4ff70033c5bb950cdbb20838e2	Fixed in 2fbd099b4e7c8c4ff70033c5bb950cdbb20838e2
LinuxLinux	Affected =5.15	Fixed in–

AI-suggested

A patch has been applied to the Linux kernel to add a sanity check for the DMC firmware load address. Users should update to a kernel version that includes commit 5e47ee5c76ca9becde8df4ad5202845b7ffcbc4c or later to ensure this vulnerability is mitigated.

Description

A vulnerability in the Linux kernel's drm/i915 driver related to the DMC firmware load address was addressed by adding a sanity check. The flaw involved the lack of validation for the firmware load address stored in dmc_info->start_mmioaddr for DMC firmware header version 3, which is used by dmc_load_program(). This could potentially allow invalid memory addresses to be used during firmware loading.

References

Community reviews

Loading reviews…