CVE-2022-50283
BaseFortify
Publication date: 2025-09-15
Last updated on: 2025-12-04
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 6.0 (inc) to 6.0.7 (exc) |
| linux | linux_kernel | 6.1 |
| linux | linux_kernel | 6.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel involves a missing call to of_node_get() in the dynamic partitions code of the mtd core subsystem. This omission leads to an unbalanced of_node_put() call, causing a use-after-free condition related to reference counting. Essentially, the kernel improperly manages the lifecycle of device tree nodes, which can result in memory corruption or instability.
How can this vulnerability impact me? :
The impact of this vulnerability is that it can cause a use-after-free error in the Linux kernel's memory management for device tree nodes. This can lead to kernel instability, crashes, or potentially allow an attacker to execute arbitrary code or cause denial of service by exploiting the memory corruption.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring the system logs for specific kernel warning messages related to unbalanced of_node_put() calls and refcount warnings. Look for kernel log entries similar to: 'refcount_t: addition on 0; use-after-free.' and 'WARNING: CPU: ... refcount_warn_saturate'. You can use the command 'dmesg | grep refcount' or 'journalctl -k | grep refcount' to check for these messages in the kernel logs.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where this vulnerability is fixed, as it addresses a missing of_node_get() call in the dynamic partitions code. Until an update is applied, monitor kernel logs for warning signs and avoid using affected MTD devices if possible.