CVE-2022-50343
Last modified
CVE-2022-50343 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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().. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
Description
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().
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 2.6.30, < 4.9.337 |
| Linux | Linux Kernel | >= 4.10, < 4.14.303 |
| Linux | Linux Kernel | >= 4.15, < 4.19.270 |
| Linux | Linux Kernel | >= 4.20, < 5.4.229 |
| Linux | Linux Kernel | >= 5.5, < 5.10.163 |
| Linux | Linux Kernel | >= 5.11, < 5.15.86 |
| Linux | Linux Kernel | >= 5.16, < 6.0.16 |
| Linux | Linux Kernel | >= 6.1, < 6.1.2 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-50343?
How severe is CVE-2022-50343?
How do I fix CVE-2022-50343?
Are you affected by CVE-2022-50343?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
