# CVE-2026-89822: drm/i915: Guard against NULL driver_data in i915_pci_probe()

> A local attacker with high privileges can cause a kernel crash by force-binding a device, leading to a NULL pointer dereference in the i915 driver.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-101136, BELL-CVE-2026-89822, DEBIAN-CVE-2026-89822, GHSA-2c46-6532-v7c3, UBUNTU-CVE-2026-89822

## What is CVE-2026-89822?

CVE-2026-89822 is a vulnerability in Linux, published on 16 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/i915: Guard against NULL driver_data in i915_pci_probe()

pci_match_device() can return the dummy pci_device_id_any entry
when a device is force-bound via sysfs driver_override, in which
case ->driver_data is unset (NULL). i915_pci_probe() casts it to
struct intel_device_info * unconditionally and dereferences
intel_info->require_force_probe, causing a NULL-ptr-deref.

(cherry picked from commit 2727922084672cc274ecea726ea00363c2893731)

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


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

Apply the vendor's patch.

## Is CVE-2026-89822 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89822 is a vulnerability in Linux, published on 16 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-89822 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-89822/ (Markdown: https://insights.sbomify.com/CVE-2026-89822/index.md)
```

## Sources

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

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