VulnerabilityPublished 17 Sep 2026Updated 21 Oct 2026

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

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in f40f3144477314b489e4bc209c06cb51679fe82b : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity

Unrated

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.
Patch: Available – fixed in f40f3144477314b489e4bc209c06cb51679fe82b, 417190bde0fda4ee857999a722ca90163fbec587, 05a1405d0cba3d8253261b02eb65e5cd3ca09ab3 +1

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

Upgrade Linux kernel to f40f3144477314b489e4bc209c06cb51679fe82b, 417190bde0fda4ee857999a722ca90163fbec587, 05a1405d0cba3d8253261b02eb65e5cd3ca09ab3 or 1d2271d7df5230e4ce36bdafd17524bd004f3b3f.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 918eb5c856f6ce4cf93b4b38e4b5e156905c5943, < f40f3144477314b489e4bc209c06cb51679fe82b	Fixed in f40f3144477314b489e4bc209c06cb51679fe82b
LinuxLinux	Affected ≥ 918eb5c856f6ce4cf93b4b38e4b5e156905c5943, < 417190bde0fda4ee857999a722ca90163fbec587	Fixed in 417190bde0fda4ee857999a722ca90163fbec587
LinuxLinux	Affected ≥ 918eb5c856f6ce4cf93b4b38e4b5e156905c5943, < 05a1405d0cba3d8253261b02eb65e5cd3ca09ab3	Fixed in 05a1405d0cba3d8253261b02eb65e5cd3ca09ab3
LinuxLinux	Affected ≥ 918eb5c856f6ce4cf93b4b38e4b5e156905c5943, < 1d2271d7df5230e4ce36bdafd17524bd004f3b3f	Fixed in 1d2271d7df5230e4ce36bdafd17524bd004f3b3f
LinuxLinux	Affected =6.12	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: iommu/tegra241-cmdqv: Fix VINTF0 leak on the init-failure path tegra241_cmdqv_init_structures() allocates VINTF0 with kzalloc_obj(), inits it, and preallocates its logical VCMDQs. Two of its error paths leak. When tegra241_cmdqv_init_vintf() fails it returns before VINTF0 reaches the cmdqv->vintfs[] array, so the devres unwind on probe failure cannot reach it; free it directly there. A later VCMDQ preallocation failure instead leaves VINTF0 published, and so this time the unwind does reach tegra241_cmdqv_remove_vintf(), which then frees it from vintf->hyp_own. But tegra241_vintf_hw_init() sets that flag only afterward, from a HW read-back, so the still-uninited VINTF0 reads as guest-owned and leaks, with mutex_destroy() and ida_destroy() run on fields it never set up. Decide ownership from vintf->idx instead, the index assigned when its id is allocated: idx 0 is the kernel-owned VINTF0, while idx >= 1 marks a guest VINTF. So the in-kernel free decision in tegra241_cmdqv_remove_vintf() and tegra241_vintf_free_lvcmdq() now keys on idx too, and hyp_own stays a pure HW-readback state.

References

Community reviews

Loading reviews…