Strix
64.3K

CVE-2026-90319

Unknown

Last modified

CVE-2026-90319 is a vulnerability of currently unknown severity. 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..

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 Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 4f3509cfcc02e9d757f2714bb7dbbeec35de6fa7, < 24f60ebabeb8757cec8ec2f97660d521bc9147ec; >= 181d4daaefb3bceeb2f2635ba9f3781eeda9e550, < 6a760a53e73064735cdfa9e51c664983a89baf96; >= ad82be4298a89a9ae46f07128bdf3d8614bce745, < 3f00999e44d9984036a029dbad9d2afe94a674d0; >= e6411c3b9512dba09af7d014d474516828c89706, < 332591a245de978349a7558f8b20469951bb77cc; >= c332f3e2df0fcae5a45fd55cc18902fb1e4825ca, < 75f0bc167b96bbbef8182b88308c732af82c8d83; >= e842f9a1edf306bf36fe2a4d847a0b0d458770de, < 44a37264b26911e13d0a4f5630751c4157ed0354; >= e842f9a1edf306bf36fe2a4d847a0b0d458770de, < 530a9d5ef831a0049dad9a6b2b92d02301352c38; >= e842f9a1edf306bf36fe2a4d847a0b0d458770de, < b74030fbf187b43c1f85b66a7082e9946511cb5d; 6d22953c4a183d0b7fdf34d68c5debd16da6edc5; a0d069ccc475abaaa79c6368ee27fc0b5912bea8; >= 5.10.235, < 5.10.270; >= 5.15.179, < 5.15.221; >= 6.1.131, < 6.1.188; >= 6.6.83, < 6.6.157; >= 6.12.19, < 6.12.110; >= 5.4.291, < 5.5; >= 6.13.7, < 6.14
LinuxLinux6.14

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-90319?
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.
How severe is CVE-2026-90319?
Severity scoring for CVE-2026-90319 is pending analysis.
How do I fix CVE-2026-90319?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-90319?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST