CVE-2026-90426
CVE CVE-2026-90426EUVD EUVD-2026-82087Published 2026-09-17T16:09:48.000Z
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: iommu/tegra241-cmdqv: Free the error IRQ before tearing down VINTFs tegra241_cmdqv_remove() tears each VINTF down first, then calls free_irq(). Tearing a VINTF down frees vintf0 and clears cmdqv->vintfs[0]. An error in that window makes tegra241_cmdqv_isr() read the stale slot and hand it to tegra241_vintf0_handle_error(), which dereferences a NULL or freed pointer. Free the IRQ before tearing the VINTFs down. free_irq() waits for in-flight handlers to finish and blocks new ones, so no ISR can observe a VINTF as it is torn down. Note: a user-owned VINTF (viommu) could outlive this teardown, which unmaps cmdqv->base and frees cmdqv->vintfs, so a later viommu close then touches freed memory. This is neither introduced nor fixed here: a physical IOMMU is not a pluggable device, so iommufd by design holds no reference on the one behind a viommu, and this teardown is not expected while that viommu is still alive.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 6.12.110; 918eb5c856f6ce4cf93b4b38e4b5e156905c5943 <076a4f5b1fc2016b973a12bc2ebb9b730e5e1e48; patch: 7.2.6; 918eb5c856f6ce4cf93b4b38e4b5e156905c5943 <421f5ab135cd4a1353891e5bf2602cfc3c01afc7; 918eb5c856f6ce4cf93b4b38e4b5e156905c5943 <735698e81f798b4c02dcb6291ffbdd1b962c8c66; 918eb5c856f6ce4cf93b4b38e4b5e156905c5943 <61f0d437988e5730b04442f6a7d30a9907339f2a; patch: 0; patch: 7.3-rc1; patch: 6.18.52; 6.12
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.