# CVE-2026-98280: drm/xe/i2c: Disable IRQ on unbind

> A use-after-free vulnerability in the Linux kernel's Intel Xe GPU driver allows local attackers to potentially execute code or escalate privileges during device unbinding.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-98280, GHSA-jc76-pp47-fx9m, UBUNTU-CVE-2026-98280

## What is CVE-2026-98280?

CVE-2026-98280 is an use after free vulnerability in Linux, published on 6 Oct 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/xe/i2c: Disable IRQ on unbind

Currently, struct xe_i2c is freed before SGUnit IRQ is disabled in unbind
path, leaving a potential UAF in case I2C IRQ is hit during this small
window. Explicitly disable I2C IRQ in xe_i2c_remove() and fix this.

(cherry picked from commit 8ba5c8b8ab3fd362267c11df2cd5a90ee46f6e24)

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


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

Apply the vendor's patch.

## Is CVE-2026-98280 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98280 is an use after free vulnerability in Linux, published on 6 Oct 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-98280 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-98280/ (Markdown: https://insights.sbomify.com/CVE-2026-98280/index.md)
```

## Sources

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

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