CVE-2025-21935

rapidio: add check for rio_add_net() in rio_scan_alloc_net()

MEDIUM

5.5

CVSS Score

Published: April 1, 2025 at 03:41 PM UTC

Updated: June 17, 2026 at 08:44 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

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: rapidio: add check for rio_add_net() in rio_scan_alloc_net() The return value of rio_add_net() should be checked. If it fails, put_device() should be called to free the memory and give up the reference initialized in rio_add_net().

Affected

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

Linux Kernel · Linux

95%

4.6 ≤ v < 5.10.2354.6 ≤ v < 5.15.1794.6 ≤ v < 5.4.2914.6 ≤ v < 6.1.1314.6 ≤ v < 6.12.194.6 ≤ v < 6.13.74.6 ≤ v < 6.144.6 ≤ v < 6.6.835.11 ≤ v < 5.15.1795.16 ≤ v < 6.1.1315.5 ≤ v < 5.10.2356.13 ≤ v < 6.13.76.2 ≤ v < 6.6.836.7 ≤ v < 6.12.194.6 6.14 rc1 6.14 rc2 6.14 rc3 6.14 rc4 6.14 rc5e6b585ca6e81badeb3d42db3cc408174f2826034

Vendor states this is fixed in 181d4daaefb3bceeb2f2635ba9f3781eeda9e550 (fixed)

Vendor states this is fixed in 4f3509cfcc02e9d757f2714bb7dbbeec35de6fa7 (fixed)

Vendor states this is fixed in 6d22953c4a183d0b7fdf34d68c5debd16da6edc5 (fixed)

Vendor states this is fixed in a0d069ccc475abaaa79c6368ee27fc0b5912bea8 (fixed)

Vendor states this is fixed in ad82be4298a89a9ae46f07128bdf3d8614bce745 (fixed)

Vendor states this is fixed in c332f3e2df0fcae5a45fd55cc18902fb1e4825ca (fixed)

Vendor states this is fixed in e6411c3b9512dba09af7d014d474516828c89706 (fixed)

Vendor states this is fixed in e842f9a1edf306bf36fe2a4d847a0b0d458770de (fixed)

Vendor states this is fixed in 4.6 (unaffected)

Vendor states this is fixed in 5.10.235 (unaffected)

Vendor states this is fixed in 5.15.179 (unaffected)

Vendor states this is fixed in 5.4.291 (unaffected)