CVE-2022-50857

rapidio: rio: fix possible name leak in rio_register_mport()

N/A

Published: December 30, 2025 at 12:15 PM UTC

Updated: June 17, 2026 at 05:24 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

N/A

Exploit prediction

EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: rapidio: rio: fix possible name leak in rio_register_mport() If device_register() returns error, the name allocated by dev_set_name() need be freed. It should use put_device() to give up the reference in the error path, so that the name can be freed in kobject_cleanup(), and list_del() is called to delete the port from rio_mports.

Affected

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

Linux Kernel · Linux

95%

3.15 ≤ v < 4.14.3033.15 ≤ v < 4.19.2703.15 ≤ v < 4.9.3373.15 ≤ v < 5.10.1633.15 ≤ v < 5.15.863.15 ≤ v < 5.4.2293.15 ≤ v < 6.0.163.15 ≤ v < 6.1.23.15 ≤ v < 6.22aaf308b95b24649a6dcfed89cd956e972089b2a3.15

Vendor states this is fixed in 0a71344f99289250e4d5b8adbac76f444485c840 (fixed)

Vendor states this is fixed in 117fede82e9d6ea3de30746d500eb5edc2eb8310 (fixed)

Vendor states this is fixed in 1bbad5793f404cf218757e3beb600eca6080330f (fixed)

Vendor states this is fixed in 4ddbeae5f224d924cf0b12460dda88c7480aa452 (fixed)

Vendor states this is fixed in 97d9eb45ffa67ffa112a6659953321b8f7db0065 (fixed)

Vendor states this is fixed in 9abba4aa60874c5216fc8de7dededadc791de696 (fixed)

Vendor states this is fixed in a47de2fd3f88a7788be19f94ade72c2244a98045 (fixed)

Vendor states this is fixed in a73a626c0510d203e369aeb26c4d6ec9c75af027 (fixed)

Vendor states this is fixed in e92a216d16bde65d21a3227e0fb2aa0794576525 (fixed)

Vendor states this is fixed in 3.15 (unaffected)

Vendor states this is fixed in 4.14.303 (unaffected)

Vendor states this is fixed in 4.19.270 (unaffected)