VulnerabilityPublished 17 Sep 2026Updated 12 Oct 2026

CVE-2026-90426: Linux kernel · iommu/tegra241-cmdqv: Free the error IRQ before tearing down VINTFs

Affects Linux kernelSource GCVE Database

Not known to be exploited.

Data as of 26 Oct 2026, 17:16 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 order of operations in the driver to free the IRQ before tearing down the VINTFs, preventing access to stale pointers. Users should update to a patched kernel version containing this fix. No additional mitigations are indicated by the vendor advisory.

Description

A vulnerability in the Linux kernel's iommu/tegra241-cmdqv driver was resolved by changing the order of freeing the error IRQ and tearing down VINTFs. Previously, tearing down VINTFs before freeing the IRQ could cause the interrupt service routine to access stale or freed memory, leading to potential NULL or use-after-free pointer dereferences. This issue affects specific Linux kernel versions used in various Ubuntu releases. The vulnerability has been fixed by freeing the IRQ before tearing down the VINTFs, ensuring no interrupt handlers observe partially torn down VINTFs.

Impact

This vulnerability could lead to kernel instability or crashes due to dereferencing NULL or freed pointers in the ISR context. It affects the iommu/tegra241-cmdqv driver in affected Linux kernel versions. There is no indication of remote code execution or privilege escalation. No known exploits in the wild have been reported.

Summary

The Linux kernel's iommu/tegra241-cmdqv driver had a vulnerability where the tegra241_cmdqv_remove() function first tore down each VINTF and then called free_irq(). Because tearing down a VINTF frees and clears related pointers, an interrupt service routine (ISR) could read stale pointers and dereference NULL or freed memory, causing potential instability or crashes. The fix involves calling free_irq() before tearing down the VINTFs, which waits for in-flight handlers to finish and blocks new ones, preventing ISRs from accessing torn down VINTFs. The advisory notes that a user-owned VINTF (viommu) could outlive this teardown, but this is not introduced or fixed by this change.

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