CVE-2022-50053
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 | 6.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-667 | The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is related to the Linux kernel's iavf driver, specifically in how it handles errors during the reset process of virtual functions (VFs). The issue arises because the error handling code incorrectly calls iavf_close during a reset failure, which leads to a double call of napi_disable and causes a deadlock. This deadlock can cause the iavf_remove task to become stuck, as it waits for a critical lock held by iavf_close. The fix involves not calling iavf_close in the reset error handling and instead calling iavf_disable_vf to properly clean up invalid resources when a reset fails.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to deadlock during rapid resets of virtual functions, leading to tasks being blocked indefinitely. This can result in system instability, including kernel panics and hung tasks, which may cause service outages or require system reboots to recover. Essentially, it can disrupt normal operation of systems using the affected driver, impacting availability and reliability.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring kernel logs for specific error messages related to the iavf driver, such as 'Failed to init adminq: -53' and messages indicating tasks blocked for more than 30 seconds involving iavf_remove or hung tasks. Checking dmesg or /var/log/kern.log for these signs can help detect the issue. Example commands include: 'dmesg | grep iavf', 'journalctl -k | grep iavf', or 'dmesg | grep "blocked for more than 30 seconds"'.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where the iavf driver reset error handling is fixed, which prevents deadlocks caused by double calls to napi_disable and stuck iavf_remove tasks. Until an update is applied, monitoring for the described error messages and avoiding rapid VF resets can reduce the risk of triggering the issue.