Strix
26.1K

CVE-2022-50669

UnknownEPSS 0.21%

Last modified

CVE-2022-50669 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: misc: ocxl: fix possible name leak in ocxl_file_register_afu() If device_register() returns error in ocxl_file_register_afu(), the name allocated by dev_set_name() need be freed. As comment of device_register() says, it should use put_device() to give up the reference in the error path. EPSS estimates a 0.21% chance of exploitation in the next 30 days.

Description

In the Linux kernel, the following vulnerability has been resolved: misc: ocxl: fix possible name leak in ocxl_file_register_afu() If device_register() returns error in ocxl_file_register_afu(), the name allocated by dev_set_name() need be freed. As comment of device_register() says, it should use put_device() to give up the reference in the error path. So fix this by calling put_device(), then the name can be freed in kobject_cleanup(), and info is freed in info_release().

Metrics

EPSS Probability
0.21%

11.4th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 75ca758adbafc81804c39b2c200ecdc819a6c042, < 0cd05062371a49774e8a45258bdedf0bd6d3d327; >= 75ca758adbafc81804c39b2c200ecdc819a6c042, < 7525741cb302a1672b8c3a5edb2a08e4229b5c7c; >= 75ca758adbafc81804c39b2c200ecdc819a6c042, < 3299983a6bf628249ac650908e62d12de959341e; >= 75ca758adbafc81804c39b2c200ecdc819a6c042, < 557b7de055d1e230ddb6664c29d26917b8db9143; >= 75ca758adbafc81804c39b2c200ecdc819a6c042, < 2fce8b3583d1641a1716486f408478b58e96ec91; >= 75ca758adbafc81804c39b2c200ecdc819a6c042, < a4cb1004aeed2ab893a058fad00a5b41a12c4691
LinuxLinux5.2

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is CVE-2022-50669?
In the Linux kernel, the following vulnerability has been resolved: misc: ocxl: fix possible name leak in ocxl_file_register_afu() If device_register() returns error in ocxl_file_register_afu(), the name allocated by dev_set_name() need be freed. As comment of device_register() says, it should use put_device() to give up the reference in the error path. So fix this by calling put_device(), then the name can be freed in kobject_cleanup(), and info is freed in info_release().
How severe is CVE-2022-50669?
Severity scoring for CVE-2022-50669 is pending analysis. The EPSS model estimates a 0.21% probability of exploitation in the next 30 days.
How do I fix CVE-2022-50669?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2022

View all 2022CVEs →

Are you affected by CVE-2022-50669?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST