CVE-2026-90430
CVE CVE-2026-90430EUVD EUVD-2026-82091Published 2026-09-17T16:09:51.000ZLast changed 2026-09-21T13:15:23.000Z
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: iommu/tegra241-cmdqv: Publish an LVCMDQ only after it is fully initialized tegra241_vintf_init_lvcmdq() stores the freshly allocated vcmdq pointer to the vintf->lvcmdqs[] array, before tegra241_vcmdq_alloc_smmu_cmdq() builds the vcmdq->cmdq. The error ISR dereferences that cmdq, so a latched LVCMDQ error (e.g. one inherited across a kexec) firing in this window would make tegra241_vintf0_handle_error() pass the still-zeroed arm_smmu_cmdq down to __arm_smmu_cmdq_skip_err(), dereferencing NULL queue register pointers. Drop the store from tegra241_vintf_init_lvcmdq() and publish the vcmdq at the end of the allocation instead, with an smp_store_release() that pairs with an smp_load_acquire() in the ISR, which can see a fully built LVCMDQ or NULL. The user-owned LVCMDQ allocation moves accordingly, publishing the vcmdq once tegra241_vcmdq_hw_init_user() succeeds, using a plain store since a user VINTF's lvcmdqs[] has no lockless reader -- the error ISR only walks the VINTF0 array.
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.18.52; 6.12; 918eb5c856f6ce4cf93b4b38e4b5e156905c5943 <792f720fc23fe5bd6508d40ed73ae739debd6dcb; patch: 0; patch: 6.12.111; patch: 7.2.6; 918eb5c856f6ce4cf93b4b38e4b5e156905c5943 <cbc41aacd49e695338940196e7084770365e1b68; 918eb5c856f6ce4cf93b4b38e4b5e156905c5943 <d5ec248ee1c79354979c23f7f390e856e9535651; 918eb5c856f6ce4cf93b4b38e4b5e156905c5943 <b4535b403d6bf9bcc24dbd62096711329b9c612c; patch: 7.3-rc1
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.