CVE-2026-90430iommu/tegra241-cmdqv: Publish an LVCMDQ only after it is fully initialized
- —Not scoredno CVSS score yet
- 0.20%Exploitation in 30 daysEPSS · top 90% 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: 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.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 32 days later
· 32 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.20% · top 90% of all CVEs (16 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 – < d5ec248ee1c79354979c23f7f390e856e9535651
- affected 918eb5c856f6ce4cf93b4b38e4b5e156905c5943 – < 792f720fc23fe5bd6508d40ed73ae739debd6dcb
- affected 918eb5c856f6ce4cf93b4b38e4b5e156905c5943 – < b4535b403d6bf9bcc24dbd62096711329b9c612c
- affected 918eb5c856f6ce4cf93b4b38e4b5e156905c5943 – < cbc41aacd49e695338940196e7084770365e1b68
- affected 6.12
- unaffected < 6.12
- unaffected 6.12.111 – ≤ 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/d5ec248ee1c79354979c23f7f390e856e9535651 (opens in a new tab)
- https://git.kernel.org/stable/c/792f720fc23fe5bd6508d40ed73ae739debd6dcb (opens in a new tab)
- https://git.kernel.org/stable/c/b4535b403d6bf9bcc24dbd62096711329b9c612c (opens in a new tab)
- https://git.kernel.org/stable/c/cbc41aacd49e695338940196e7084770365e1b68 (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-82091 (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-90430)Record last updated .