CVE-2026-90426: iommu/tegra241-cmdqv: Free the error IRQ before tearing down VINTFs
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Fixed version: Linux Linux 076a4f5b1fc2016b973a12bc2ebb9b730e5e1e48, 421f5ab135cd4a1353891e5bf2602cfc3c01afc7, 61f0d437988e5730b04442f6a7d30a9907339f2a.
Low priority for now. Upgrade to Linux Linux 076a4f5b1fc2016b973a12bc2ebb9b730e5e1e48, 421f5ab135cd4a1353891e5bf2602cfc3c01afc7, 61f0d437988e5730b04442f6a7d30a9907339f2a or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: iommu/tegra241-cmdqv: Free the error IRQ before tearing down VINTFs tegra241_cmdqv_remove() tears each VINTF down first, then calls free_irq(). Tearing a VINTF down frees vintf0 and clears cmdqv->vintfs[0]. An error in that window makes tegra241_cmdqv_isr() read the stale slot and hand it to tegra241_vintf0_handle_error(), which dereferences a NULL or freed pointer. Free the IRQ before tearing the VINTFs down. free_irq() waits for in-flight handlers to finish and blocks new ones, so no ISR can observe a VINTF as it is torn down. Note: a user-owned VINTF (viommu) could outlive this teardown, which unmaps cmdqv->base and frees cmdqv->vintfs, so a later viommu close then touches freed memory. This is neither introduced nor fixed here: a physical IOMMU is not a pluggable device, so iommufd by design holds no reference on the one behind a viommu, and this teardown is not expected while that viommu is still alive.
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 9th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.12affected
- 918eb5c856f6ce4cf93b4b38e4b5e156905c5943 and later · before 076a4f5b1fc2016b973a12bc2ebb9b730e5e1e48affected · git
- 918eb5c856f6ce4cf93b4b38e4b5e156905c5943 and later · before 735698e81f798b4c02dcb6291ffbdd1b962c8c66affected · git
- 918eb5c856f6ce4cf93b4b38e4b5e156905c5943 and later · before 421f5ab135cd4a1353891e5bf2602cfc3c01afc7affected · git
- 918eb5c856f6ce4cf93b4b38e4b5e156905c5943 and later · before 61f0d437988e5730b04442f6a7d30a9907339f2aaffected · git
- before 6.12not affected · semver
- 6.12.110 and later · up to and including 6.12.*not affected · semver
- 6.18.52 and later · up to and including 6.18.*not affected · semver
- 7.2.6 and later · up to and including 7.2.*not affected · semver
- 7.3 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-90424Sep 17, 2026 · iommu/tegra241-cmdqv: Fix VINTF0 leak on the init-failure path0Monitor
- ← EarlierCVE-2026-90425Sep 17, 2026 · iommu/tegra241-cmdqv: Require exactly one Stream ID for a vSID35Monitor
- Later →CVE-2026-90427Sep 17, 2026 · iommu/tegra241-cmdqv: Don't fall back to a freed smmu after devm_krealloc()29Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 076a4f5b1fc2016b973a12bc2ebb9b730e5e1e48 | Vendor (CNA) |
| Linux Linux | 421f5ab135cd4a1353891e5bf2602cfc3c01afc7 | Vendor (CNA) |
| Linux Linux | 61f0d437988e5730b04442f6a7d30a9907339f2a | Vendor (CNA) |
| Linux Linux | 735698e81f798b4c02dcb6291ffbdd1b962c8c66 | Vendor (CNA) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.