VulnerabilityPublished 17 Sep 2026Updated 5 Oct 2026

CVE-2026-90430: Linux kernel · iommu/tegra241-cmdqv: Publish an LVCMDQ only after it is fully initialized

Affects Linux kernelSource GCVE Database

Not known to be exploited.

Data as of 26 Oct 2026, 14:05 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.04 LTSlinux`pkg:deb/ubuntu/linux?arch=source&distro=resolute`Other threats	Affected 6.17.0-5.5 – 7.0.0-38.38 23 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-aws`pkg:deb/ubuntu/linux-aws?arch=source&distro=resolute`Other threats	Affected 6.17.0-1002.2 – 7.0.0-1014.14 15 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-azure`pkg:deb/ubuntu/linux-azure?arch=source&distro=resolute`Other threats	Affected 6.17.0-1003.3 – 7.0.0-1017.17 15 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-azure-fde`pkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resolute`Other threats	Affected 7.0.0-1003.3 – 7.0.0-1016.16 9 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-gcp`pkg:deb/ubuntu/linux-gcp?arch=source&distro=resolute`Other threats	Affected 6.17.0-1002.2 – 7.0.0-1014.14 13 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-gke`pkg:deb/ubuntu/linux-gke?arch=source&distro=resolute`Other threats	Affected 7.0.0-1002.3 – 7.0.0-1008.9 6 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available that changes the initialization sequence to publish the LVCMDQ only after it is fully initialized, using memory barriers to ensure safe access. Users should update to patched kernel versions that include this fix. Since this is a kernel-level issue, applying the official kernel updates from the vendor is the recommended remediation.

Description

A vulnerability in the Linux kernel's iommu/tegra241-cmdq component was fixed by ensuring that an LVCMDQ structure is only published after it is fully initialized. Previously, a partially initialized pointer could be dereferenced by an error interrupt service routine, leading to NULL pointer dereferences. This issue affects specific Linux kernel versions used in various Ubuntu LTS releases.

Impact

The vulnerability can cause NULL pointer dereferences in the kernel's error handling path for the iommu/tegra241-cmdq component. This may lead to kernel crashes or instability when a latched LVCMDQ error occurs, such as one inherited across a kexec. There is no indication of code execution or privilege escalation from the provided data.

Summary

The vulnerability involves the premature publication of a freshly allocated vcmdq pointer to the vintf->lvcmdqs[] array before the vcmdq->cmdq is fully built. If an error interrupt fires during this window, it may cause the error ISR to dereference a NULL queue register pointer, leading to potential kernel errors. The fix drops the early store and publishes the vcmdq only after full initialization using appropriate memory barriers to ensure safe concurrent access. This change prevents the ISR from accessing an uninitialized LVCMDQ structure.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Oct 2026, 22:57 UTC

Technical details

References

Community reviews

Related threats