CVE-2022-50669
published 2025-12-09CVE-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…
PriorityP417low5.5
EPSS
0.25%
16.2th percentile
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().
Affected
17 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.4-1 (bookworm) | linux 6.1.4-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 75ca758adbafc81804c39b2c200ecdc819a6c042 < 0cd05062371a49774e8a45258bdedf0bd6d3d327 | 0cd05062371a49774e8a45258bdedf0bd6d3d327 |
| linux | linux | >= 75ca758adbafc81804c39b2c200ecdc819a6c042 < 7525741cb302a1672b8c3a5edb2a08e4229b5c7c | 7525741cb302a1672b8c3a5edb2a08e4229b5c7c |
| linux | linux | >= 75ca758adbafc81804c39b2c200ecdc819a6c042 < 3299983a6bf628249ac650908e62d12de959341e | 3299983a6bf628249ac650908e62d12de959341e |
| linux | linux | >= 75ca758adbafc81804c39b2c200ecdc819a6c042 < 557b7de055d1e230ddb6664c29d26917b8db9143 | 557b7de055d1e230ddb6664c29d26917b8db9143 |
| linux | linux | >= 75ca758adbafc81804c39b2c200ecdc819a6c042 < 2fce8b3583d1641a1716486f408478b58e96ec91 | 2fce8b3583d1641a1716486f408478b58e96ec91 |
| linux | linux | >= 75ca758adbafc81804c39b2c200ecdc819a6c042 < a4cb1004aeed2ab893a058fad00a5b41a12c4691 | a4cb1004aeed2ab893a058fad00a5b41a12c4691 |
| linux | linux_kernel | >= 0 < 5.10.178-1 | 5.10.178-1 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 5.11.0 < 5.15.86 | 5.15.86 |
| linux | linux_kernel | >= 5.16.0 < 6.0.16 | 6.0.16 |
| linux | linux_kernel | >= 5.2.0 < 5.4.229 | 5.4.229 |
| linux | linux_kernel | >= 5.5.0 < 5.10.163 | 5.10.163 |
| linux | linux_kernel | >= 6.1.0 < 6.1.2 | 6.1.2 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: misc: ocxl: fix possible name leak in ocxl_file_register_afu()
vendor_redhat·2025-12-09·CVSS 5.5
CVE-2022-50669 [LOW] CWE-911 kernel: misc: ocxl: fix possible name leak in ocxl_file_register_afu()
kernel: misc: ocxl: fix possible name leak in ocxl_file_register_afu()
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().
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 corr
Debian
CVE-2022-50669: linux - In the Linux kernel, the following vulnerability has been resolved: misc: ocxl:...
vendor_debian·2022
CVE-2022-50669 CVE-2022-50669: linux - In the Linux kernel, the following vulnerability has been resolved: misc: ocxl:...
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().
Scope: local
bookworm: resolved (fixed in 6.1.4-1)
bullseye: resolved (fixed in 5.10.178-1)
forky: resolved (fixed in 6.1.4-1)
sid: resolved (fixed in 6.1.4-1)
trixie: resolved (fixed in 6.1.4-1)
OSV
misc: ocxl: fix possible name leak in ocxl_file_register_afu()
osv·2025-12-09
CVE-2022-50669 misc: ocxl: fix possible name leak in ocxl_file_register_afu()
misc: ocxl: fix possible name leak in ocxl_file_register_afu()
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().
GHSA
GHSA-ffpg-m95f-r6q9: In the Linux kernel, the following vulnerability has been resolved:
misc: ocxl: fix possible name leak in ocxl_file_register_afu()
If device_registe
ghsa_unreviewed·2025-12-09
CVE-2022-50669 GHSA-ffpg-m95f-r6q9: In the Linux kernel, the following vulnerability has been resolved:
misc: ocxl: fix possible name leak in ocxl_file_register_afu()
If device_registe
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().
OSV
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(
osv·2025-12-09
CVE-2022-50669 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(
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().
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/0cd05062371a49774e8a45258bdedf0bd6d3d327https://git.kernel.org/stable/c/2fce8b3583d1641a1716486f408478b58e96ec91https://git.kernel.org/stable/c/3299983a6bf628249ac650908e62d12de959341ehttps://git.kernel.org/stable/c/557b7de055d1e230ddb6664c29d26917b8db9143https://git.kernel.org/stable/c/7525741cb302a1672b8c3a5edb2a08e4229b5c7chttps://git.kernel.org/stable/c/a4cb1004aeed2ab893a058fad00a5b41a12c4691
2025-12-09
Published