CVE-2022-50462
BaseFortify
Publication date: 2025-10-01
Last updated on: 2026-01-16
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.30 (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 involves a possible memory leak in the Linux kernel's MIPS vpe-mt module when the module is exiting. After a certain commit, the device name is allocated dynamically and needs to be freed properly by calling put_device() to release the reference. The vpe_device is static, so the previous method of freeing memory (kfree()) was removed from vpe_device_release(). The fix ensures that memory is correctly freed to prevent leaks.
How can this vulnerability impact me? :
The vulnerability can cause a memory leak in the Linux kernel module, which may lead to increased memory usage and potentially degrade system performance or stability over time if the module is frequently loaded and unloaded.