iommu/tegra241-cmdqv: Fix VINTF0 leak on the init-failure path

Summary

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.

Timeline

1. Sep 17, 2026, 4:09 PM UTCCVE published
2. Oct 21, 2026, 12:51 PM UTCRecord last updated

Affected versions

• Linux Linux

  From 918eb5c856f6ce4cf93b4b38e4b5e156905c5943 · fixed in 05a1405d0cba3d8253261b02eb65e5cd3ca09ab3; From 918eb5c856f6ce4cf93b4b38e4b5e156905c5943 · fixed in 1d2271d7df5230e4ce36bdafd17524bd004f3b3f; From 918eb5c856f6ce4cf93b4b38e4b5e156905c5943 · fixed in 417190bde0fda4ee857999a722ca90163fbec587; From 918eb5c856f6ce4cf93b4b38e4b5e156905c5943 · fixed in f40f3144477314b489e4bc209c06cb51679fe82b

• Linux Linux

  6.12

• KernelLinux

  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

References 4