CVE-2022-50160
BaseFortify
Publication date: 2025-06-18
Last updated on: 2025-11-18
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) |
| 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-NVD-CWE-Other |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a reference count leak in the Linux kernel's mtd maps component, specifically in the ap_flash_init function. The function of_find_matching_node() returns a node pointer with its reference count incremented, but the code was missing a call to of_node_put() to decrement the reference count when the node is no longer needed. This missing call causes a reference count leak.
How can this vulnerability impact me? :
The reference count leak can lead to resource leaks in the kernel, potentially causing increased memory usage or instability over time. However, the exact impact depends on the system usage and workload.
What immediate steps should I take to mitigate this vulnerability?
Apply the Linux kernel update that includes the fix for the refcount leak in ap_flash_init by ensuring the patch that adds the missing of_node_put() call is applied. This will prevent the refcount leak issue.