# CVE-2026-93068: drm/amd/display: Fix DM I2C teardown race

> A race condition in the AMD display driver allows local attackers to trigger a kernel NULL pointer dereference and system crash during device removal.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-93068, DEBIAN-CVE-2026-93068, GHSA-qm88-w7fg-5vv2, UBUNTU-CVE-2026-93068

## What is CVE-2026-93068?

CVE-2026-93068 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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

## Which versions are affected by CVE-2026-93068?


## How do I fix CVE-2026-93068?

Apply the vendor's patch.

## Is CVE-2026-93068 being exploited?

There is no known exploitation of CVE-2026-93068 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93068 and fix it if it is affected.

What it is: CVE-2026-93068 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93068 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93068/ (Markdown: https://insights.sbomify.com/CVE-2026-93068/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93068
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93068
- OSV: https://osv.dev/vulnerability/CVE-2026-93068

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93068/
Summaries are generated and may contain mistakes; the official description above is the record.