CVE-2022-49994
BaseFortify
Publication date: 2025-06-18
Last updated on: 2025-11-14
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.0 |
| linux | linux_kernel | 6.0 |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
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 the Linux kernel's memory leak detector (kmemleak) incorrectly handling vmemmap pages allocated from memblock. Specifically, when freeing these pages, they were not properly removed from kmemleak's tracking, causing kmemleak to report errors and disable itself. This happens because kmemleak tries to insert overlapping memory objects into its search tree, leading to malfunction.
How can this vulnerability impact me? :
The impact of this vulnerability is that the kernel's memory leak detector (kmemleak) may stop working correctly, potentially disabling memory leak detection. This could make it harder to identify and fix actual memory leaks in the kernel, possibly leading to undetected memory issues and system instability.