VulnerabilityPublished 17 Sep 2026Updated 19 Oct 2026

CVE-2026-93068: Linux kernel · drm/amd/display: Fix DM I2C teardown race

Affects Linux kernelSource CVE Database V5

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

Data as of 26 Oct 2026, 12:55 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in e4ae30a12aa95942814957d8bc1ce7366a7107d7, 6970ec944567f109ac4240f9aea58158ee8a18cd, 8ee385305e8902fa6fbfd66b5a112238292567b6

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Sep 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.

What to do

Upgrade Linux kernel to e4ae30a12aa95942814957d8bc1ce7366a7107d7, 6970ec944567f109ac4240f9aea58158ee8a18cd or 8ee385305e8902fa6fbfd66b5a112238292567b6.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 5b3eca05cfb02ed0dbd7097c056fb08ce5f76fe3, < e4ae30a12aa95942814957d8bc1ce7366a7107d7	Fixed in e4ae30a12aa95942814957d8bc1ce7366a7107d7
LinuxLinux	Affected ≥ 5b3eca05cfb02ed0dbd7097c056fb08ce5f76fe3, < 6970ec944567f109ac4240f9aea58158ee8a18cd	Fixed in 6970ec944567f109ac4240f9aea58158ee8a18cd
LinuxLinux	Affected ≥ 5b3eca05cfb02ed0dbd7097c056fb08ce5f76fe3, < 8ee385305e8902fa6fbfd66b5a112238292567b6	Fixed in 8ee385305e8902fa6fbfd66b5a112238292567b6
LinuxLinux	Affected =6.18	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix DM I2C teardown race DM I2C adapters can remain visible to userspace while DM teardown is already in progress. A concurrent i2c-dev transfer may then enter amdgpu_dm_i2c_xfer() after the backing DM state has been torn down, leading to a NULL pointer dereference. Create a devres group around the DM I2C adapter lifetime and release it at the start of dm_hw_fini(), before HPD, IRQ, and DM state are torn down. This removes the I2C adapters first and waits for in-flight users to drain before the structures used by amdgpu_dm_i2c_xfer() disappear. This fixes a teardown ordering race seen during device removal: BUG: kernel NULL pointer dereference RIP: amdgpu_dm_i2c_xfer+0x122/0x1c0 [amdgpu] Call Trace: __i2c_transfer i2c_transfer i2cdev_ioctl_rdwr

References

Community reviews

Loading reviews…