CVE-2026-90424iommu/tegra241-cmdqv: Fix VINTF0 leak on the init-failure path
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 34 days later
· 34 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 918eb5c856f6ce4cf93b4b38e4b5e156905c5943 – < 05a1405d0cba3d8253261b02eb65e5cd3ca09ab3
- affected 918eb5c856f6ce4cf93b4b38e4b5e156905c5943 – < 1d2271d7df5230e4ce36bdafd17524bd004f3b3f
- affected 918eb5c856f6ce4cf93b4b38e4b5e156905c5943 – < 417190bde0fda4ee857999a722ca90163fbec587
- affected 918eb5c856f6ce4cf93b4b38e4b5e156905c5943 – < f40f3144477314b489e4bc209c06cb51679fe82b
- affected 6.12
- unaffected < 6.12
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.52 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References4
- https://git.kernel.org/stable/c/05a1405d0cba3d8253261b02eb65e5cd3ca09ab3 (opens in a new tab)
- https://git.kernel.org/stable/c/1d2271d7df5230e4ce36bdafd17524bd004f3b3f (opens in a new tab)
- https://git.kernel.org/stable/c/417190bde0fda4ee857999a722ca90163fbec587 (opens in a new tab)
- https://git.kernel.org/stable/c/f40f3144477314b489e4bc209c06cb51679fe82b (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-82085 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-90424)Record last updated .