# CVE-2026-90428: iommu/tegra241-cmdqv: Don't run the error ISR before probe sets up vintfs

> A race condition in the Tegra241 CMDQV driver causes a null pointer dereference during early interrupt handling, leading to a kernel crash.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-90428, DEBIAN-CVE-2026-90428, GHSA-gjw5-xf6c-mcgq, UBUNTU-CVE-2026-90428

## What is CVE-2026-90428?

CVE-2026-90428 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

iommu/tegra241-cmdqv: Don't run the error ISR before probe sets up vintfs

__tegra241_cmdqv_probe() requests the error IRQ before it has allocated the
cmdqv->vintfs array and set cmdqv->num_vintfs. A CMDQV left enabled with a
latched error across a kexec fires the IRQ as soon as it is requested, and
tegra241_cmdqv_isr() then walks the uninitialized cmdqv->vintfs array.

Request the IRQ only after cmdqv->vintfs is allocated and zeroed, so that
a latched interrupt firing early runs the ISR against a valid array of NULL
slots that it safely skips.

## Which versions are affected by CVE-2026-90428?


## How do I fix CVE-2026-90428?

Apply the vendor's patch.

## Is CVE-2026-90428 being exploited?

There is no known exploitation of CVE-2026-90428 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90428 and fix it if it is affected.

What it is: CVE-2026-90428 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-90428 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-90428/ (Markdown: https://insights.sbomify.com/CVE-2026-90428/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90428
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90428
- OSV: https://osv.dev/vulnerability/CVE-2026-90428

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90428/
Summaries are generated and may contain mistakes; the official description above is the record.