CVE-2026-90319 — rapidio: clear mport->net when rio_add_net() fails
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
version a0d069ccc475abaaa79c6368ee27fc0b5912bea8version 6.14≥ 6.13.7 and < 6.14≥ 5.4.291 and < 5.5≥ 6.12.19 and < 6.12.110≥ 6.6.83 and < 6.6.157≥ 6.1.131 and < 6.1.188≥ 5.15.179 and < 5.15.221 and 10 more≥ 5.10.235 and < 5.10.270≥ 4f3509cfcc02e9d757f2714bb7dbbeec35de6fa7 and < 24f60ebabeb8757cec8ec2f97660d521bc9147ecversion 6d22953c4a183d0b7fdf34d68c5debd16da6edc5≥ e842f9a1edf306bf36fe2a4d847a0b0d458770de and < b74030fbf187b43c1f85b66a7082e9946511cb5d≥ e842f9a1edf306bf36fe2a4d847a0b0d458770de and < 530a9d5ef831a0049dad9a6b2b92d02301352c38≥ e842f9a1edf306bf36fe2a4d847a0b0d458770de and < 44a37264b26911e13d0a4f5630751c4157ed0354≥ c332f3e2df0fcae5a45fd55cc18902fb1e4825ca and < 75f0bc167b96bbbef8182b88308c732af82c8d83≥ e6411c3b9512dba09af7d014d474516828c89706 and < 332591a245de978349a7558f8b20469951bb77cc≥ ad82be4298a89a9ae46f07128bdf3d8614bce745 and < 3f00999e44d9984036a029dbad9d2afe94a674d0≥ 181d4daaefb3bceeb2f2635ba9f3781eeda9e550 and < 6a760a53e73064735cdfa9e51c664983a89baf96 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 18, 2026 · 3 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/24f60ebabeb8757cec8ec2f97660d521bc9147ec
- git.kernel.org/stable/c/44a37264b26911e13d0a4f5630751c4157ed0354
- git.kernel.org/stable/c/3f00999e44d9984036a029dbad9d2afe94a674d0
- git.kernel.org/stable/c/332591a245de978349a7558f8b20469951bb77cc
- git.kernel.org/stable/c/75f0bc167b96bbbef8182b88308c732af82c8d83
- git.kernel.org/stable/c/6a760a53e73064735cdfa9e51c664983a89baf96
- git.kernel.org/stable/c/530a9d5ef831a0049dad9a6b2b92d02301352c38
- git.kernel.org/stable/c/b74030fbf187b43c1f85b66a7082e9946511cb5d
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 17h
- Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 17h
- Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 17h
- Unknown CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 17h
- Unknown CVE-2026-98857 ipvs: bound LBLCR and LBLC cache growth 17h
- Unknown CVE-2026-98858 io_uring: fix task_work add use-after-free with SQPOLL 17h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-90319 is "rapidio: clear mport->net when rio_add_net() fails", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.