CVE-2026-90430
Last modified
CVE-2026-90430 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.20% chance of exploitation in the next 30 days.
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 918eb5c856f6ce4cf93b4b38e4b5e156905c5943, < d5ec248ee1c79354979c23f7f390e856e9535651; >= 918eb5c856f6ce4cf93b4b38e4b5e156905c5943, < 792f720fc23fe5bd6508d40ed73ae739debd6dcb; >= 918eb5c856f6ce4cf93b4b38e4b5e156905c5943, < b4535b403d6bf9bcc24dbd62096711329b9c612c; >= 918eb5c856f6ce4cf93b4b38e4b5e156905c5943, < cbc41aacd49e695338940196e7084770365e1b68 |
| Linux | Linux | 6.12 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-90430?
How severe is CVE-2026-90430?
How do I fix CVE-2026-90430?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-90424In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90425In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-90426In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90427In the Linux kernel, the following vulnerability has been re…7.4
- CVE-2026-90428In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90429In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-90431In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90432In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90433In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90434In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90435In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-90439NGINX Plus and NGINX Open Source have a vulnerability in the…6.5
Are you affected by CVE-2026-90430?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
