CVE-2022-50055
BaseFortify
Publication date: 2025-06-18
Last updated on: 2025-11-13
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 | 6.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability involves improper error handling in the iavf driver of the Linux kernel. Specifically, when allocating DMA coherent memory for the VF mailbox, if an error occurs during the configuration of ASQ/ARQ registers, the allocated DMA memory is not freed properly. This leads to memory leaks of DMA regions when the network interface is unloaded.
How can this vulnerability impact me? :
The impact of this vulnerability is that it can cause memory leaks in the DMA regions used by the iavf driver. This can lead to resource exhaustion or instability in the system when the network interface is unloaded, potentially affecting system performance or causing unexpected behavior.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by observing error messages related to DMA allocations when unloading the network interface. Specifically, look for messages like: 'dma_debug_device_change: device driver has pending DMA allocations while released from device [count=32]'. You can check the system logs using commands such as 'dmesg | grep dma_debug_device_change' or 'journalctl -k | grep dma_debug_device_change' to identify these errors.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Linux kernel to a version where the iavf driver has the fix for proper adminq error handling and freeing of DMA regions during ASQ/ARQ configuration errors. This prevents DMA memory leaks when unloading the interface. Until then, monitor for the described error messages and avoid unloading the interface unnecessarily.