{"id":"CVE-2026-90424","summary":"iommu/tegra241-cmdqv: Fix VINTF0 leak on the init-failure path","details":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu/tegra241-cmdqv: Fix VINTF0 leak on the init-failure path\n\ntegra241_cmdqv_init_structures() allocates VINTF0 with kzalloc_obj(), inits\nit, and preallocates its logical VCMDQs. Two of its error paths leak.\n\nWhen tegra241_cmdqv_init_vintf() fails it returns before VINTF0 reaches the\ncmdqv-\u003evintfs[] array, so the devres unwind on probe failure cannot reach\nit; free it directly there.\n\nA later VCMDQ preallocation failure instead leaves VINTF0 published, and so\nthis time the unwind does reach tegra241_cmdqv_remove_vintf(), which then\nfrees it from vintf-\u003ehyp_own. But tegra241_vintf_hw_init() sets that flag\nonly afterward, from a HW read-back, so the still-uninited VINTF0 reads as\nguest-owned and leaks, with mutex_destroy() and ida_destroy() run on fields\nit never set up.\n\nDecide ownership from vintf-\u003eidx instead, the index assigned when its id is\nallocated: idx 0 is the kernel-owned VINTF0, while idx \u003e= 1 marks a guest\nVINTF. So the in-kernel free decision in tegra241_cmdqv_remove_vintf() and\ntegra241_vintf_free_lvcmdq() now keys on idx too, and hyp_own stays a pure\nHW-readback state.","modified":"2026-09-18T03:48:38.454269246Z","published":"2026-09-17T16:09:47.165Z","database_specific":{"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90424.json","cna_assigner":"Linux"},"references":[{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"},{"type":"WEB","url":"https://git.kernel.org/stable/c/1d2271d7df5230e4ce36bdafd17524bd004f3b3f"},{"type":"WEB","url":"https://git.kernel.org/stable/c/417190bde0fda4ee857999a722ca90163fbec587"},{"type":"WEB","url":"https://git.kernel.org/stable/c/f40f3144477314b489e4bc209c06cb51679fe82b"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90424.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90424"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"918eb5c856f6ce4cf93b4b38e4b5e156905c5943"},{"fixed":"1d2271d7df5230e4ce36bdafd17524bd004f3b3f"},{"fixed":"417190bde0fda4ee857999a722ca90163fbec587"},{"fixed":"f40f3144477314b489e4bc209c06cb51679fe82b"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-90424.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.0"},{"fixed":"6.18.52"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.2.6"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-90424.json"}}],"schema_version":"1.9.0"}