Bug 2420380 (CVE-2022-50669)

Summary: CVE-2022-50669 kernel: misc: ocxl: fix possible name leak in ocxl_file_register_afu()
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedKeywords: Security
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A memory leak vulnerability was found in the OpenCAPI (ocxl) driver in the Linux kernel. In ocxl_file_register_afu(), when device_register() fails, the name string allocated by dev_set_name() is not properly freed. The fix uses put_device() to correctly release resources through kobject_cleanup().
 Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2025-12-09 02:07:03 UTC 
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().
Comment 1 Alexander B 2025-12-09 14:46:02 UTC 
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025120945-CVE-2022-50669-f124@gregkh/T