# CVE-2026-90319: rapidio: clear mport->net when rio_add_net() fails

> A use-after-free vulnerability in the Linux kernel RapidIO subsystem allows local attackers to cause a denial of service or potentially execute code via dangling pointer dereference.

- **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:** AZL-101879, BELL-CVE-2026-90319, DEBIAN-CVE-2026-90319, GHSA-2x23-jxch-r563, UBUNTU-CVE-2026-90319

## What is CVE-2026-90319?

CVE-2026-90319 is an use after free 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:

rapidio: clear mport->net when rio_add_net() fails

rio_alloc_net() stores the newly allocated rio_net in mport->net before
rio_scan_alloc_net() registers the device.

If rio_add_net() fails, rio_scan_alloc_net() drops the device reference
with put_device(), which releases the rio_net through the device release
callback.  However, mport->net is left pointing at the freed object.

A later mport unregister path can then dereference the dangling mport->net
pointer and may try to free the same rio_net again.

Clear mport->net in the rio_add_net() failure path, matching the cleanup
done for the destID table allocation failure path.

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


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

Apply the vendor's patch.

## Is CVE-2026-90319 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90319 is an use after free 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-90319 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-90319/ (Markdown: https://insights.sbomify.com/CVE-2026-90319/index.md)
```

## Sources

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

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