CVE-2022-50343 json
rapidio: fix possible name leaks when rio_add_device() fails
published 2025-09-16 13 mo ago modified 2026-06-17 4 mo ago also EUVD-2022-55619
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
rapidio: fix possible name leaks when rio_add_device() fails
Patch series "rapidio: fix three possible memory leaks".
This patchset fixes three name leaks in error handling. - patch #1 fixes two name leaks while rio_add_device() fails. - patch #2 fixes a name leak while rio_register_mport() fails.
This patch (of 2):
If rio_add_device() 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 the 'rdev' can be freed in rio_release_dev().
Patch / fix
- Linux Linux 4.9.337, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2, 6.2
- linux Debian 14, Debian 13, Debian 12 6.1.4-1
debian advisories DEBIAN-CVE-2022-50343
- linux Ubuntu 18.04 LTS 4.15.0-208.220
- linux Ubuntu 20.04 LTS 5.4.0-144.161
- linux Ubuntu 22.04 LTS 5.15.0-69.76
- linux-aws Ubuntu 18.04 LTS 4.15.0-1153.166
- linux-aws Ubuntu 20.04 LTS 5.4.0-1097.105
- linux-aws Ubuntu 22.04 LTS 5.15.0-1033.37
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1101.110
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1031.38
ubuntu advisories UBUNTU-CVE-2022-50343
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/3b4676f274a6b5d001176f15d0542100bbf4b59a commit
- git.kernel.org/stable/c/c482cb0deb57924335103fe592c379a076d867f8 commit
- git.kernel.org/stable/c/80fad2e53eaed2b3a2ff596575f65669e13ceda5 commit
- git.kernel.org/stable/c/440afd7fd9b164fdde6fc9da8c47d3d7f20dcce8 commit
- git.kernel.org/stable/c/88fa351b20ca300693a206ccd3c4b0e0647944d8 commit
- git.kernel.org/stable/c/ec3f04f74f50d0b6bac04d795c93c2b852753a7a commit
- git.kernel.org/stable/c/c413f65011ff8caffabcde0e1c3ceede48a48d6f commit
- git.kernel.org/stable/c/85fbf58b15c09d3a6a03098c1e42ebfe9002f39d commit
- git.kernel.org/stable/c/f9574cd48679926e2a569e1957a5a1bcc8a719ac commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-50343 updated
kernel: rapidio: fix possible name leaks when rio_add_device() fails
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 9 mo ago
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-401 Missing Release of Memory after Effective Lifetime
- Technology feeds
References
-
git.kernel.org
/stable/c/3b4676f274a6b5d001176f15d0542100bbf4b59a
patch
-
git.kernel.org
/stable/c/c482cb0deb57924335103fe592c379a076d867f8
patch
-
git.kernel.org
/stable/c/80fad2e53eaed2b3a2ff596575f65669e13ceda5
patch
-
git.kernel.org
/stable/c/440afd7fd9b164fdde6fc9da8c47d3d7f20dcce8
patch
-
git.kernel.org
/stable/c/88fa351b20ca300693a206ccd3c4b0e0647944d8
patch
-
git.kernel.org
/stable/c/ec3f04f74f50d0b6bac04d795c93c2b852753a7a
patch
-
git.kernel.org
/stable/c/c413f65011ff8caffabcde0e1c3ceede48a48d6f
patch
-
git.kernel.org
/stable/c/85fbf58b15c09d3a6a03098c1e42ebfe9002f39d
patch
-
git.kernel.org
/stable/c/f9574cd48679926e2a569e1957a5a1bcc8a719ac
patch
Sources
- CVE List CVE-2022-50343
- NVD CVE-2022-50343
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.