misc: ocxl: fix possible name leak in ocxl_file_register_afu()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 75ca758adbafc81804c39b2c200ecdc819a6c042 · < a4cb1004aeed2ab893a058fad00a5b41a12c4691| No fix yet |
| Linux Linux |
|
|
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().
From the CVE record · Linux
The Linux kernel can leak an allocated device name if device_register() fails in ocxl_file_register_afu(). The input does not describe how an attacker could trigger the error or whether access or user interaction is required.
Engineers running Linux kernels with the ocxl component should check their versions; affected versions were not provided.