CVE-2022-50352
BaseFortify
Publication date: 2025-09-16
Last updated on: 2025-12-01
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 4.4 (inc) to 4.9.332 (exc) |
| linux | linux_kernel | From 4.10 (inc) to 4.14.298 (exc) |
| linux | linux_kernel | From 4.15 (inc) to 4.19.264 (exc) |
| linux | linux_kernel | From 4.20 (inc) to 5.4.221 (exc) |
| linux | linux_kernel | From 5.5 (inc) to 5.10.152 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.76 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.0.6 (exc) |
| linux | linux_kernel | 6.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-401 | The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a possible memory leak in the Linux kernel's network driver module hns, specifically in the function hnae_ae_register(). When the device_register() function fails during module probing, the reference count of a kernel object (kobject) is not properly decreased to zero. As a result, the name allocated in dev_set_name() is not freed, causing a memory leak. The fix involves calling put_device() to ensure the name is freed during the kobject_cleanup() callback.
How can this vulnerability impact me? :
This vulnerability can lead to a memory leak in the Linux kernel when certain network driver modules fail to register devices properly. Over time, this memory leak could cause increased memory usage, potentially degrading system performance or stability, especially on systems that frequently load and unload these modules or experience device registration failures.