CVE-2022-50074
BaseFortify
Publication date: 2025-06-18
Last updated on: 2025-11-17
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| 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 is a memory leak in the Linux kernel's AppArmor component, specifically in the function aa_simple_write_to_buffer(). When the function copy_from_user fails, only part of the allocated memory is freed, causing a memory leak because the management structure and data blob are allocated separately. The fix involves properly freeing all allocated memory using aa_put_loaddata(data).
How can this vulnerability impact me? :
This vulnerability can lead to a memory leak in the Linux kernel, which may cause increased memory usage and potentially degrade system performance or stability over time if exploited or triggered repeatedly.
What immediate steps should I take to mitigate this vulnerability?
Update the Linux kernel to a version that includes the fix for the memleak in aa_simple_write_to_buffer(), where aa_put_loaddata(data) is used to properly free memory. This will prevent the memory leak caused by improper freeing of allocated memory in AppArmor. No other mitigation steps are provided.