CVE-2026-90319

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

N/A
Published: September 17, 2026 at 04:08 PM UTC
Updated: October 19, 2026 at 09:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

181d4daaefb3bceeb2f2635ba9f3781eeda9e5504f3509cfcc02e9d757f2714bb7dbbeec35de6fa75.10.2355.15.1795.4.2916.1.1316.12.196.13.76.146.6.836d22953c4a183d0b7fdf34d68c5debd16da6edc5a0d069ccc475abaaa79c6368ee27fc0b5912bea8ad82be4298a89a9ae46f07128bdf3d8614bce745c332f3e2df0fcae5a45fd55cc18902fb1e4825cae6411c3b9512dba09af7d014d474516828c89706e842f9a1edf306bf36fe2a4d847a0b0d458770de
Vendor states this is fixed in 24f60ebabeb8757cec8ec2f97660d521bc9147ec (fixed)
Vendor states this is fixed in 332591a245de978349a7558f8b20469951bb77cc (fixed)
Vendor states this is fixed in 3f00999e44d9984036a029dbad9d2afe94a674d0 (fixed)
Vendor states this is fixed in 44a37264b26911e13d0a4f5630751c4157ed0354 (fixed)
Vendor states this is fixed in 530a9d5ef831a0049dad9a6b2b92d02301352c38 (fixed)
Vendor states this is fixed in 6a760a53e73064735cdfa9e51c664983a89baf96 (fixed)
Vendor states this is fixed in 75f0bc167b96bbbef8182b88308c732af82c8d83 (fixed)
Vendor states this is fixed in b74030fbf187b43c1f85b66a7082e9946511cb5d (fixed)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.14 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card