VulnerabilityPublished 17 Sep 2026Updated 5 Oct 2026

CVE-2026-90424: Linux kernel · iommu/tegra241-cmdqv: Fix VINTF0 leak on the init-failure path

Affects Linux kernelSource GCVE Database

Authoritative record:CVE-2026-90424

Not known to be exploited.

Data as of 26 Oct 2026, 13:47 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% 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 for this vulnerability has been implemented in the Linux kernel source code by correcting the ownership logic for VINTF0 freeing. Users should apply the updated Linux kernel versions containing this fix. Patch status is not explicitly stated in the input data, so check the vendor or distribution advisory for the specific fixed kernel versions and apply updates accordingly.

Description

A vulnerability in the Linux kernel's iommu/tegra241-cmdqv component caused a resource leak of the VINTF0 structure on certain initialization failure paths. The issue arises because error handling paths either fail to free the allocated VINTF0 or incorrectly determine its ownership, leading to leaks and improper cleanup operations. The fix involves changing the ownership decision logic to rely on the vintf->idx index rather than a hardware-readback flag, ensuring proper resource deallocation.

Impact

The vulnerability causes a resource leak of the VINTF0 structure during initialization failure in the iommu/tegra241-cmdqv driver. This leak can lead to improper cleanup and potential instability or resource exhaustion in affected systems. There is no indication of direct code execution or privilege escalation from this issue.

Summary

The Linux kernel vulnerability CVE-2026-90424 involves the iommu/tegra241-cmdqv driver where the VINTF0 structure allocated by tegra241_cmdqv_init_structures() leaks on two error paths during initialization. When tegra241_cmdqv_init_vintf() fails, VINTF0 is not added to the cmdqv->vintfs[] array, preventing devres from freeing it on probe failure, so it must be freed directly. Another error path leaves VINTF0 published but with an uninitialized hyp_own flag, causing it to be misidentified as guest-owned and thus leaked. The fix changes the ownership determination to use vintf->idx (index 0 for kernel-owned VINTF0, >=1 for guest VINTFs) instead of the hyp_own hardware-readback flag, ensuring correct freeing of VINTF0 in tegra241_cmdqv_remove_vintf() and tegra241_vintf_free_lvcmdq().

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