CVE-2022-50349
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 2.6.22 (inc) to 4.9.337 (exc) |
| linux | linux_kernel | From 4.10 (inc) to 4.14.303 (exc) |
| linux | linux_kernel | From 4.15 (inc) to 4.19.270 (exc) |
| linux | linux_kernel | From 4.20 (inc) to 5.4.229 (exc) |
| linux | linux_kernel | From 5.5 (inc) to 5.10.163 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.86 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.0.16 (exc) |
| linux | linux_kernel | From 6.1 (inc) to 6.1.2 (exc) |
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 tifm driver, specifically in the tifm_7xx1_switch_media() function. If device_register() returns an error, the name of a kobject allocated during device_add() is leaked because the device is not properly freed. The correct procedure is to use put_device() to release the reference instead of directly freeing the device.
How can this vulnerability impact me? :
The impact of this vulnerability is a potential memory leak in the kernel, which could lead to increased memory usage and possibly degrade system performance or stability over time if the leak occurs repeatedly.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, ensure that the Linux kernel is updated to a version where the fix for the memory leak in tifm_7xx1_switch_media() is applied. Avoid directly freeing the device after calling device_register(), and instead use put_device() to properly release the reference. Applying the official kernel patch or update that addresses this issue is recommended.